On 18/03/2011 2:40 AM, Barney Carroll wrote:
On 17 March 2011 14:01, Alan Gresley<[email protected]> wrote:
I saying that IE7 compatibility mode in IE8 was somewhat wrong and IE7
compatibility mode in IE9 is very wrong. The following test cases are for
IE9 RC. In IE7 compatibility mode, the bugs are not present.
I just found a slightly more helpful description of the intended
effects of X-UA-Compatible headers and emulation modes on MSDN here:
http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx#SetMode.
It turns out I'd got things wrong, since setting a browser mode in the
DOM inspector forces standards mode — as does setting the meta tag
value to IE#. Setting the value to Emulate=IE# apparently does more
accurate emulation, since it allows for standards or quirks mode to be
established based on the usual factors. Further inaccuracy on my part:
'compatibility mode' apparently forces IE7 in standards mode. So for
those still reading, I retract all of my verbose nonsense 2 emails
back.
The test.
<http://css-class.com/test/bugs/ie/5~7/ie-pee-ka-boo-bug.htm>
Firstly press F12 and observe that the page default is IE7. This test
case has the corrcet header,
<meta http-equiv="X-UA-Compatible" content="IE=7" />
and a IE7 conditional comment and an IE7 CSS hack. I can not see any
pee-ka-boo activity.
<http://css-class.com/test/bugs/ie/renderingbands-image-size.htm>
I would please appreciate a check of the above test case in the the latest
version of IE9 since I have IE9 RC.
I couldn't find instructions on how to perform the tests whose results
are listed in that table (page looks substantially different for each
of the last 3 versions of IE though!). However:
1. Rendering bands:
Can't replicate any of the bugs
In IE7 compatibility mode in IE8 you could.
2. Escaping floats
Can replicate all the bugs forced IE7 mode and compatibility mode
If you can replicate the IE7 bug, you would also be able to rub out the
unstable parts with a small window.
3. Sons of suckerfish
Can't replicate any of the bugs
4. Recalculate offset
Can't replicate any of the bugs
5. Button crash
Can't replicate
6. Background flicker
Can't replicate any
7. Em font-sizing inheritance
Can't replicate
7. Em font-sizing inheritance
Can't replicate
8. Strange peekaboo
In IE7 mode and compatibility mode, the blue-bordered div simply
doesn't appear unless the viewport width is less than 337px, and
although its top offset is immediately within the parent's border (as
one would hope), the 'test' divs inside it within in clear the
red-bordered div. At viewport sizes under 262px, the blue border still
wraps the content, but the background colour only fills the top 18px.
This doesn't seem to be the behaviour you're describing, but then it's
inherently weird stuff.
I stand disconcerted and corrected!
What you observe is what I can see in IE9 RC. What version of IE are you
testing in Barney?
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
