Alex Robinson wrote:
Now, as an aside and not being particularly expert on quirks mode
rendering, are there any specific differences (other than the ones
just discussed) that anyone is aware of between IE6 quirks mode and
IE7 quirks mode? (I'm fully aware of their being many standards mode
I've seen a couple of other cases (not related to parsing/selectors
problems but to rendering) where IE8 quirks is equal to IE7 quirks
when this differs from IE6 quirks.
Also, I just noticed (again, this may be old news by now) that
fieldsets and input buttons (and presumably all form
On Sun, Mar 9, 2008 at 2:55 AM, Alan Gresley wrote:
What about using the ID class selector bug or the last class bug.
http://www.brettschultz.com/ie6_exhibit_a.html
IE8 in IE5 quirks mode is showing the last test Aqua. and first and second
test red.
IE6 will show red, red,
You now have your quirks mode documents with no doctype.
If I put in a quirks mode doctype (HTML 4.01 Transitional, no url)
then IE8 behavior in those two cases changes. It sees the *+html, as
with a standard doctype, like the X-UA IE=8 or 7 overrode the quirks
mode of the document. This is more
Alex Robinson wrote:
I've added a second quirks mode to both the iframe demos and the hack
filters. As you said, the HTML4 without a URL provokes the expected
quirks behaviour with regard to * html.
http://local.fu2k.org/alex/css/cssjunk/ie8/xua
Alan Gresley wrote:
http://annevankesteren.nl/2008/03/ie8-bad#comment-6499
All I want is a stand alone IE8 in super duper standard mode. We now
have to support:
1. The real IE5 (optional) 2. The real IE6 3. The real IE7
and one of the following.
4a. IE8 Standard mode 4b. IE7 Strict
Gunlaug Sørtun wrote:
Alan Gresley wrote:
http://annevankesteren.nl/2008/03/ie8-bad#comment-6499
All I want is a stand alone IE8 in super duper standard mode. We now
have to support:
1. The real IE5 (optional) 2. The real IE6 3. The real IE7
and one of the following.
Alan Gresley wrote:
http://css-class.com/images/gunlang.png
You wouldn't have used display:table any where perhaps?
Yes, and I wouldn't dream of making changes until IE8 is fixed and
stable. It's the browser that's broken, not the design.
If they are serious about CSS 2.1 support, then it
In IE6 all lines are of equal length. So this would mean that IE8
is emulating the quirks modes different to how
IE6 and IE7 handle quirks mode. Is this correct?
Nope. Or rather I don't think so. I think your original suggestion was correct.
ie. IE=5 actually causes IE8 to emulate IE6 in
On Sat, Mar 8, 2008 at 8:54 PM, Alex Robinson [EMAIL PROTECTED] wrote:
ie. IE=5 actually causes IE8 to emulate IE6 in quirks mode. End of story.
My error was to use documents in standards mode as the reference
point. I have now updated
http://www.fu2k.org/alex/css/cssjunk/ie8/xua
Alex Robinson wrote:
IE=8
---
The only hack / target combination which does not jibe, is the fact
the *+html hack also gets applied by IE8 when targeted as IE=8.
To repeat *+html targets IE8[0]. Since this only
I mostly agree, but not on the Rendered by IE 7 and quirks
combinations. Your documents now have an xml declaration at the
beginning which puts IE6 in quirks mode, but NOT IE7.
The Rendered by IE 7 row should be exactly as the Rendered by IE 6 row.
The screengrabs I'm using are exactly how IE7 (a
On Sat, Mar 8, 2008 at 10:22 PM, Alex Robinson
[EMAIL PROTECTED] wrote:
Ah, I see what you mean. The way I have made it go into quirks mode
is not actually making IE7 go into quirks mode. My lazy bad. I'll
change it so it actually uses a quirks-causing doctype.
Done.
You're right
At this point I think it's hard to say if with X_UA IE=5IE8 is
emulating IE7 quirks or IE6 quirks, simply because the two are hardly
distinguishable (I guess is more IE7 than IE6.)
Yes, my previous claim that we know it's IE6 was founded on the
assumption that I was serving quirks mode
On Sun, Mar 9, 2008 at 12:18 AM, Alex Robinson wrote:
When X-UA is IE=7 or 8 and the doc is in quirks mode, then things go
slightly awry.
[...]
But in quirks mode, IE8 ignores both * html and * + html (again for
both IE=7 and IE=8).
You now have your quirks mode documents with no
Bruno Fassino wrote:
On Sat, Mar 8, 2008 at 10:22 PM, Alex Robinson wrote:
Ah, I see what you mean. The way I have made it go into quirks mode
is not actually making IE7 go into quirks mode. My lazy bad. I'll
change it so it actually uses a quirks-causing doctype.
Done.
You're right
16 matches
Mail list logo
