29 Jan 2012 7:45 PM #1
[4.1 B2] Panel with an unterminated tag messes up layout in IE8
REQUIRED INFORMATION Ext version tested:
- Ext 4.1 rev B2
- FF5 (firebug 1.8.1)
- Having an unterminated font tag "<font>" in the HTML body of a panel messes up the layout in IE. It's messed up on both the file system or on a Windows 2008R2 webserver, but it's messed up slightly differently. Works ok in FF5 and works ok with 4.0.7 in all environments. I realize this is probably fixable on my side by closing out the font tag, but I'll be trying to drop 4.1 into an existing project that someone else built and am trying to mitigate any out of the box upgrade issues possible.
- Make a panel with html: '<font>'. I tried to find other tags that would break the layout and didn't see any during testing, though I just test a handful.
- A panel laid out with no layout issues (as if there was no html property at first glance).
- The panel is shifted down about 20px. On the file system the bottom border is missing and the panel title is shifted down by about 1 pixel.
- not provided
- only default ext-all.css
- WinXP Pro
File System example
Windows 2008R2 webserver
30 Jan 2012 1:07 PM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
This technically isn't an Ext JS bug IMO... your HTML is invalidMitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
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 email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
30 Jan 2012 1:15 PM #3
Yeah, I thought about not even posting this. Last week I inherited an existing application running on Ext 2.2 and was working on porting it to 4.x. It was working ok on 4.0.7 so I tried loading up 4.1 B2 and started just picking off issues as I found them. Don had mentioned that he wanted to make sure that everything that was working in 4.0.x was working ok in 4.1 so figured I'd post since the same html was working without incident in 2.2 and 4.0.7.
But, I'm good closing this one. Buggier than 4.0.7, but not a bug.