[4.1 B2] Button menu separated from shadow

[4.1 B2] Button menu separated from shadow

REQUIRED INFORMATIONExt version tested:

Ext 4.1 rev B2

Browser versions tested against:

IE8

FF5 (firebug 1.8.1)

DOCTYPE tested against:

strict

Description:

Button menu is separated from its shadow. The shadow is in the right place, but the menu is not. Happens on IE 8 and FF 5. Layout is just fine when run from the file system, but is detached when run from a Windows 2008 webserver with IIS7. We have projects on Ext 2.2, 3.x, and 4.0.7 running on that same server successfully. Running the same script on 4.0.7 works ok.

Steps to reproduce the problem:

click on the button to reveal its menu

The result that was expected:

the menu should be directly below the button

The result that occurs instead:

The menu's shadow is where it should be, but the button's menu is not.

On our corporate images 70% of folks have IE7 and 30% IE8 and some 15-20% have FF5. I can test IE9 at home off of the corporate image as well as Chrome 17 and FF 9, but those I can only test on the file system or on my Apache platform. Since all of the dev work I do is for corp imaged machines I've been trying to debug 4.1 Beta on the IE8 / FF5 machine only.

The screenshots I did before were from IE. Here is what I'm seeing on FF when published to our corp Windows 2008R2 server. First is the 4.1 Beta 2 screenshot. The second one I pointed to 4.0.7 gpl and republished. Both taken using FF5 with firebug 1.8.1 on a Windows XP Pro box.

I was having some difficult with compatibility mode in IE and I turned that off to make sure that wasn't causing problems in IE. Still see the shadow disconnect with IE running in browser mode: IE8 and document mode: IE8 Standards.

And still in FF, as well, but have only had a chance to test on FF5 with firebug 1.8.1.

1000 apologies.
I figured it out. In the past when auditioning code I'd take an existing file and point the ext-all.js lib to the new version and test. If all's well then I'd roll apps over to a newer version. Not a great practice if I don't also point to the latest css file, too. When no one else was complaining or could reproduce the anomalies I knew it was something I was doing, but couldn't figure out what.

Sorry for the wasted effort looking for bugs that just weren't there. Please consider this thread closed.