IE8: "On the path to Web Standards Compliance"
Moderator: General Moderators
- Maugrim_The_Reaper
- DevNet Master
- Posts: 2704
- Joined: Tue Nov 02, 2004 5:43 am
- Location: Ireland
- John Cartwright
- Site Admin
- Posts: 11470
- Joined: Tue Dec 23, 2003 2:10 am
- Location: Toronto
- Contact:
Re: IE8: "On the path to Web Standards Compliance"
I certainly spoke too soon! This is freaking ridiculous.. IE8 standards mode.. what a joke.Wikipedia: Internet Explorer wrote: However, the version of IE8 that will be released will not pass Acid2 as it will require pages to specifically request to be rendered in IE8 standards mode, and Acid2 does not request this.
Re: IE8: "On the path to Web Standards Compliance"
I knew it. We're witnessing MS trying to claim credit for something they never did. This time it's "Setting the web standard"
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact:
- RobertGonzalez
- Site Administrator
- Posts: 14293
- Joined: Tue Sep 09, 2003 6:04 pm
- Location: Fremont, CA, USA
Re: IE8: "On the path to Web Standards Compliance"
Sometimes I wish IE could be shot in the face with a bazooka.
- Ollie Saunders
- DevNet Master
- Posts: 3179
- Joined: Tue May 24, 2005 6:01 pm
- Location: UK
Silly rabbits
Calm down everyone. Firefox works in exactly the same way. Have you never right-clicked and choosen page info? What's the third bit of information there --- "Render Mode". You turn on standards mode by using the appropriate doctype. XHTML doctype definitely does it, I think strict HTML 4.01 might as well. This has been the case for ages already and is the reason why all those sites using deprecated markup still look how they did back in the 90s. Opera and Safari won't handle deprecated markup correctly because they don't have this feature. Separate quirks and standards modes is a good thing, really.
- RobertGonzalez
- Site Administrator
- Posts: 14293
- Joined: Tue Sep 09, 2003 6:04 pm
- Location: Fremont, CA, USA
Re: IE8: "On the path to Web Standards Compliance"
The one thing that article doesn't say is what triggers IE8 Standards mode. Knowing them, you will have to put some non-standard MS proprietary tag in the markup to make it render that way.
Or better yet, you would have to change a setting in your IE options to render a page in standards mode. For each page.
Or better yet, you would have to change a setting in your IE options to render a page in standards mode. For each page.
- Ollie Saunders
- DevNet Master
- Posts: 3179
- Joined: Tue May 24, 2005 6:01 pm
- Location: UK
Re: IE8: "On the path to Web Standards Compliance"
Why would that do it like that? So that all standards compliant pages render incorrectly? Nobody wants that. They would hardly go to all the effort of implementing all that compliance stuff without having it be applied sensibly.
- RobertGonzalez
- Site Administrator
- Posts: 14293
- Joined: Tue Sep 09, 2003 6:04 pm
- Location: Fremont, CA, USA
Re: IE8: "On the path to Web Standards Compliance"
Kinda like they did with IE7 
I am just a basher of MS until they show me that can do it correctly, which they haven't.
I am just a basher of MS until they show me that can do it correctly, which they haven't.
- Ollie Saunders
- DevNet Master
- Posts: 3179
- Joined: Tue May 24, 2005 6:01 pm
- Location: UK
Re: IE8: "On the path to Web Standards Compliance"
Well, better a Microsoft basher than an open source one, I guess.
Re: IE8: "On the path to Web Standards Compliance"
The difference between Firefox & IE in this case would be the way they turn on standards mode. Firefox is choosing the appropriate mode for the document. If the document says it's written in a standardized way (by setting a DOCTYPE), then Firefox uses that mode.
The difference is that IE (it appears) wouldn't use any standard, established way of communicating what rendering mode to use & would instead (and yet again) use their own proprietary method.
The difference is that IE (it appears) wouldn't use any standard, established way of communicating what rendering mode to use & would instead (and yet again) use their own proprietary method.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
- Ollie Saunders
- DevNet Master
- Posts: 3179
- Joined: Tue May 24, 2005 6:01 pm
- Location: UK
IE 6 and 7's both use the doctype in order to identify standards compliance already, why would they change and invent something new? I guess you could argue that they are maniacs, but then you could say anything:
If you really wanna bash Microsoft start with their plans to ignore the open document standard, that really is an abomination.
Your all speculating anyway. Don't just bash Microsoft because it's fashionable (god when will the fashion ever end!). Yes, they do some pretty stupid, arrogant stuff but for once one particular team working for Microsoft is showing that it is listening to the people and has worked hard to achieve it. Give them a break ffs! Remember when you make comments about the IE developers you are referring to real people.Mr. Daz Says-Anything wrote:I proclaim that in the next release of IE Microsoft are undoubtedly going to force web authors to choose from a limited "Microsoft-certified" colour pallet, featuring only lime green, hot fuchsia pink, puke brown and cyan.
If you really wanna bash Microsoft start with their plans to ignore the open document standard, that really is an abomination.
Re:
Why would they? They were a considerable force in its standardization after all.ole wrote:If you really wanna bash Microsoft start with their plans to ignore the open document standard, that really is an abomination.
Re: Re:
By implementing their own, "semi-open/closed" format OOXML instead of the real open Open Document Format?Weirdan wrote:Why would they? They were a considerable force in its standardization after all.ole wrote:If you really wanna bash Microsoft start with their plans to ignore the open document standard, that really is an abomination.
Re:
So it appears Mr. Daz Says-Anything is right. They did invent something new.ole wrote:IE 6 and 7's both use the doctype in order to identify standards compliance already, why would they change and invent something new? I guess you could argue that they are maniacs, but then you could say anything:Mr. Daz Says-Anything wrote:I proclaim that in the next release of IE Microsoft are undoubtedly going to force web authors to choose from a limited "Microsoft-certified" colour pallet, featuring only lime green, hot fuchsia pink, puke brown and cyan.
Please read the new article on alistapart about IE8? http://www.alistapart.com/articles/beyonddoctype
More on http://annevankesteren.nl/2008/01/ie-lock-in and http://blogs.msdn.com/ie/archive/2008/0 ... d-ie8.aspx
This is insane. They want to use some new form of browser sniffing by using meta tags! Now web developers not only need to set conditional comments to target specific IE versions, but meta tags as well. They are afraid they will break the web with new versions of their browser. Guess what Microsoft, you already broke the web with your browsers.
I say, again, stop developing IE. Let it die slowly and let everybody switch to any of the other great browsers out there.
If we would follow Microsoft, our webpages will look like this in a few years:
Code: Select all
<html some Doctype here, I think. Maybe. />
<head>
[b]<meta http-equiv="X-UA-Compatible" content="IE=8;FF=3;OtherUA=4" />[/b]
<!-- bugger, did I forget some browsers?? -->
<!-- IF IE6 -->
// ...
<!--ENDIF-->
<!-- IF IE5 -->
// ...
<!--ENDIF-->
<style>
/* @IE8:supermode=true */
#normal{ rules-go:here;
}
</style>
</head>
..