PDA

View Full Version : [DUP] [EXTJSIV-3449] Ext 3-4 CSS issues with isIE7 and isIE8



Ron Howard
28 Jun 2011, 10:28 AM
REQUIRED INFORMATION

*** Not sure which bug number this is but here is both of them.

EXTJSIV-3449
EXTJSIV-3467

Ext version tested:


Ext 4.0+
Ext 3.0+



Browser versions tested against:


IE7/8



Description:


Using meta tags and DOCTYPE to make IE's document mode be either 7 or 8 engine makes Ext detect IE7 in Compat mode causing css to be wrong.



Steps to reproduce the problem:


Using IE8 developer's tools to have browser mode of IE8 compatible mode.
Change between document mode of IE7 and IE8 you can see the ext-ie7 is used even when 8 is choosen.
I used
<!DOCTYPE html>
<meta http-equiv="X-UA-Compatible" content="IE=8; IE=7;">


The result that was expected:


from javascript object document.documentMode you can tell what the desired engine is being used. When IE8 is used should have ext-ie8 css.

The result that occurs instead:


ext-ie7 css tag is used instead

HELPFUL INFORMATION

Possible fix:


I made an override to go against what number document.documentMode is set too and turned on the correct isIE7 or isIE8 properties to true to fix the issue before ext-all.js loads.



Additional CSS used:


only default ext-all.css



Operating System:


Windows

Ron Howard
30 Jun 2011, 6:16 AM
Ext 4
Bug:
26836
Correct:
26837

Ron Howard
11 Jul 2011, 8:16 AM
Ext 3.4:

Bug:
26933

Correct:
26935

edspencer
11 Jul 2011, 12:33 PM
Thanks for the detailed report, it's in our bug tracker now

Ron Howard
12 Jul 2011, 10:17 AM
Thanks Ed. I have a small code snippet to fix it for what I needed but wouldn't be a perm fix.
If you want to look at that just let me know.

Also not sure which bug number is the correct one so I will let you guys change the topic if it's the wrong bug number.

:)

edspencer
12 Jul 2011, 11:13 AM
I actually duped it by mistake - the ticket number in the title is the correct one. I'll see if I can fix that

Ron Howard
5 Aug 2011, 6:59 AM
Any word on this bug?
After I fixed the isIE7 and isIE8 with compat mode a lot of the quirky bugs our project was having went away.
I am sure it will be helping you as well. :)

Ron Howard
19 Aug 2011, 8:50 AM
Any updates on this bug issue?
It's been 2 weeks since my last post.

Just curious where things are going.

Thanks,
Ron

edspencer
22 Aug 2011, 10:03 AM
We have some higher priority issues we're addressing first. If you could post your override so we can verify the correction that would probably speed things up

Ron Howard
22 Aug 2011, 12:57 PM
Here is a quick snippet of what I'm using between ext-base.js and ext-all.js in Ext 3.1.1. My code for Ext 3.1.1 works correctly in IE9 also with no css issues at all when using this.
All the IE7 and IE8 css fixes I had I didn't need anymore because Ext was setting the wrong flag for the documentmode IE was in. This also fixed any layout bugs I had for 3.
Thats when I tested Ext 4 and found in Compat mode Ext was setting both IE7 and IE8 css tags like my screenshot above.


if(Ext.isIE === true && Ext.isIE7 === true && document.documentMode && document.documentMode === 8) {
Ext.isIE7 = false;
Ext.isIE8 = true;
} else if(Ext.isIE === true && Ext.isIE8 === true && document.documentMode && document.documentMode === 7) {
Ext.isIE7 = true;
Ext.isIE8 = false;
}

edspencer
22 Aug 2011, 1:00 PM
Ok, I've sent one of our guys to check this out. If we roll a 4.0.7 it will likely make it into that

Ron Howard
22 Aug 2011, 1:03 PM
Is 4.0.6 coming out this week?
I still have a few issues with Menu that wasn't addressed in 4.0.5.

Thanks Ed.

Ron

edspencer
24 Aug 2011, 1:48 PM
Is 4.0.6 coming out this week?
I still have a few issues with Menu that wasn't addressed in 4.0.5.

Thanks Ed.

Ron

Yes, just one bug left now

dnickels
25 Oct 2011, 7:48 AM
+1 on this bug causing problems for my company. This has become a serious issue for us trying to migrate our flagship app (which is an intranet based app that we deploy on customer intranet servers) to more up-to-date standards. We've tested the 4.0.7 code base, but the fix for the issue isn't present in that stream of code. Any word on which version of ExtJs will contain the fix?

Ron Howard
25 Oct 2011, 8:49 AM
I'm at SenchaCon and will ask the guys what the status is on this bug and try to find more information about it.

Ron Howard
7 Feb 2012, 12:44 PM
Give a small update on this. At SenchaCon I showed the guys it was still broken at least for isiE7 in 4.0.7.
I took a look and Ext JS 4.1 beta 1 has this finally fixed.
Ext JS 4.1 pr1 had the same as 4.0.7 when Don and I looked at it on his laptop after one of the sessions.

Ext JS 3+ hasn't had any updates yet and probably won't have any public release.