CSS Support Could Be IE7's Weakest Link
Ritalin16 writes "Many web developers may be disappointed to hear that Microsoft decided to hold off on full CSS2 support with IE 7.0. As said by Microsoft-Watch: 'One partner said that Microsoft considers CSS2 to be a flawed standard and that the company is waiting for a later point release, such as CSS2.1 or CSS3, before throwing its complete support behind it.'" More commentary available from ZDNet. Generally related to the IE 7 Acid Test thrown down by Opera.
We consider the standard to be flawed. So instead we will continue with our flawed support of the previous standard.
Has anyone ever justified these claims that CSS is a flawed standard? In slashdotters experience, is CSS flawed, and if so, how?
Get a free iPod Nano 4GB!
What. Just because their products have their own flaws means they should adopt all technologies that are flawed?
"Ideas without action are worthless."
if by "adheres quite reasonably" you mean "enough errors on the main page that the w3c validator gave up and stopped counting after the first 50", then yes, slashdot adheres quite reasonably to HTML 3.2.
If I don't put anything here, will anyone recognize me anymore?
The real reason why Microsoft does not fully embrace W3C standards is because they want to move away from browser-based application. This is also the reason why they let IE development go into the tank.
In the browser-based application model, MS does not control the desktop. They have competitions from Firefox and Opera. More importantly, MS also does not control the server. They have competition not only from Apache, but also Google, Amazon, eBay, AOL, and anyone who publishes a web application.
Microsoft's aim is to control both ends of a network application. And the way they are going to do this is to replace HTTP web servers with IIS and Exchange Server and to replace web browsers with Outlook. The .NET platform is just a step towards that goal. If you accept IIS/Exchange and Outlook as a server/client network application platform, there is no need for W3C standards. It also eliminates any competition, or at least make the competition dependent on Microsoft technologies.
Therefore, any effort that Microsoft expends into making "the web" more usable, such as CSS compliance and updates to IE, only enhances the browser-based application model and hurts Microsoft in the long run.
CSS 2.0 (or even 2.1) being *so* unbelievably tough to implement is probably the reason why no one managed to create IE5.x and IE6 CSS "patches"...
oh wait, it's been done, and with only Javascript
Rewrite large parts of the browser, yeah, right...
"The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler