-
29 Jan 2012 3:50 PM #1
[4.1 B2] Button menu separated from shadow
[4.1 B2] Button menu separated from shadow
REQUIRED INFORMATION Ext version tested:
- Ext 4.1 rev B2
- IE8
- FF5 (firebug 1.8.1)
- strict
- 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.
- click on the button to reveal its menu
- the menu should be directly below the button
- The menu's shadow is where it should be, but the button's menu is not.
HELPFUL INFORMATION Screenshot or Video:Code:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>Tabs Example</title> <!-- Ext includes --> <link rel="stylesheet" type="text/css" href="../../resources/css/ext-all.css" /> <link rel="stylesheet" type="text/css" href="../../resources/css/BoxSelect.css" /> <script type="text/javascript" src="../../ext-all.js"></script> <script type="text/javascript" src="../../BoxSelect.js"></script> <script type="text/javascript"> Ext.onReady(function () { Ext.create('Ext.Button', { text: 'Menu button', renderTo: Ext.getBody(), arrowAlign: 'bottom', menu: [ { text: 'Item 1' }, { text: 'Item 2' }, { text: 'Item 3' }, { text: 'Item 4' } ] }); }); </script> </head> <body> </body> </html>- attached
- none
- not provided
- only default ext-all.css
- WinXP Pro
menu_shadow.PNGscreenshot is from IE8. FF5 is similar.
-
30 Jan 2012 12:46 PM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,656
- Vote Rating
- 435
I don't have IE8 but on Chrome 16, FF4, IE6 this all looks as expected.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
30 Jan 2012 1:11 PM #3
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.
4.1 B2
menu_shadow_ff.PNG
4.0.7 gpl
menu_shadow_ff_on_407.PNG
-
31 Jan 2012 7:30 AM #4
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.
-
31 Jan 2012 12:35 PM #5
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.
Looks like we can't reproduce the issue or there's a problem in the test case provided.


Reply With Quote