To view parent comment, click here.
To read all comments associated with this story, please click here.
Exactly, it is Microsoft's own fault we have to worry about millions of non-standards compliant web pages!! I remember when web-programming meant looking at the standards, and adhering to them properly.
When did web-programming mean looking at the standards? Microsoft's been around way too long for me to remember such times..And don't be so bitter, there's some delightful irony in this whole situation too!
Think about it, for years Microsoft made sure that their browser would be The Browser to support and so the pages designed for it would not display as well on other browsers..Then came all the alternative platforms and browsers, pushing for standards-compliance, and now that Microsoft has finally given in to the demand they have to add quirks to their own browser to support the non-standards-compliant way their browsers used to behave
That must suck :3






Member since:
2005-07-24
Exactly, it is Microsoft's own fault we have to worry about millions of non-standards compliant web pages!! I remember when web-programming meant looking at the standards, and adhering to them properly.
If you had the wrong doc-type, you got the wrong result.
All the extra handling by the browsers means the internet will never become standards compliant, but will rather just work well enough ( creating greater obstacles to overcome in order to effectively compete with MS ( that is the idea anyway )).
I would rather have every web-page using exacting standardized methods than having my browser fall-back into a guessing game ( while consuming more energy and RAM ) just so pages designed for Internet Explorer ( or maybe even just malformed HTML X.x ) will look somewhat close to how they are meant to look.
Hrm, but no one is willing to go that far. (it would make it seem like your browser is the one that sucks, when it is in reality the web pages which suck ).
--The loon