- Related Stories
-
Open-source divorce for Apple's Safari?
May 12, 2005 -
Microsoft discloses some IE 7 plans
April 25, 2005 -
The Acid2 challenge to Microsoft
March 16, 2005
In its browser blog, Microsoft acknowledged that IE 7 would not pass the Web Standards Project's Acid2 test, which examines a browser's support for W3C (World Wide Web Consortium) recommendations including CSS1 (Cascading Style Sheets), HTML4 and PNG (Portable Network Graphics).
"We will not pass this test when IE7 ships," Chris Wilson, lead program manager for the Web platform in IE, wrote in the IE blog. "We fully recognize that IE is behind the game today in CSS support. We've dug through the Acid2 test and analyzed IE's problems with the test in some great detail, and we've made sure the bugs and features are on our list--however, there are some fairly large and difficult features to implement, and they will not all sort to the top of the stack in IE7."
Standards advocates and Web developers have criticized Microsoft for letting Internet Explorer go without a significant upgrade for years. This spring it became clear that Microsoft would finally address long-standing standards-compliance issues in its planned version 7 upgrade.
Microsoft last week came out with a test, or "beta" version, of its Windows Vista operating system and IE 7.
Wilson said the broad range of Acid2's demands made it more of a "wish list" than a "compliance test."
"As a wish list, it is really important and useful to my team, but it isn't even intended, in my understanding, as our priority list for IE7," Wilson wrote.
The Web Standards Project responded positively to the announcement, hailing Microsoft's standards to-do list and its openness in acknowledging the test.
"While it doesn't hit everything we might like, and we won't see most of it until Beta 2, it's a pretty impressive list for a release that by all accounts is primarily about security and UI features," Web Standards Project member Chris Kaminski wrote. "Even more impressive than the contents of the list, though, is that it's even available outside the Redmond campus. Having been through this 'work with Microsoft' thing once before in the late '90s, I can assure you this sort of openness is a radical departure from the Microsoft of old and as good a reason as any for optimism that this is just the beginning, and we can expect even more and better in IE 7.5 and beyond."
The Web Standards Project launched seven years ago to goad Microsoft and Netscape into heeding W3C recommendations. These days, the group takes a less confrontational approach than it used to, working closely with software companies like Macromedia and Microsoft before products are released.
Microsoft's competitors sounded a less forgiving note in responding to the news.
"I think they should take the time required to do this right," said Hakon Lie, chief technology officer of Opera Software in Oslo, Norway, who threw down the Acid2 gauntlet to Microsoft in a News.com column this spring. "We're not going to see another IE for another several years, and this is their chance to show that they really care about standards, as they've been saying. They've used so many years to create IE 7, they can take the extra month required to make it pass."
Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.
See more CNET content tagged:
Microsoft Internet Explorer 7, Opera Software, standards, CSS, Microsoft Internet Explorer



people. Web standards are just a 'wish list' for MS? And
compliance with those standards is not a priority item with MS?
Says a lot, doesn't it? "Damn the specifications, full speed ahead"
continues to be MS's battle cry.
Maybe if this latest bit of MS fog is treated as a positive event,
actual code improvement might eventiually show up.
Meanwhile, I will put IE 7 on my wish list with some miniscule
priority, like maybe zero? After all, I already have FireFox, Opera,
Camino, and Safari. So there just isn't much room left for IE 7,
even if Windows Uodate requires it.
priority, like maybe zero? After all, I already have FireFox, Opera,
Camino, and Safari. So there just isn't much room left for IE 7,
even if Windows Uodate requires it."""
Realy Safari on windows???? Where can I get it???
people. Web standards are just a 'wish list' for MS? And
compliance with those standards is not a priority item with MS?
Says a lot, doesn't it? "Damn the specifications, full speed ahead"
continues to be MS's battle cry.
Maybe if this latest bit of MS fog is treated as a positive event,
actual code improvement might eventiually show up.
Meanwhile, I will put IE 7 on my wish list with some miniscule
priority, like maybe zero? After all, I already have FireFox, Opera,
Camino, and Safari. So there just isn't much room left for IE 7,
even if Windows Uodate requires it.
priority, like maybe zero? After all, I already have FireFox, Opera,
Camino, and Safari. So there just isn't much room left for IE 7,
even if Windows Uodate requires it."""
Realy Safari on windows???? Where can I get it???
Do it or don't complain.
Unless Bill says ok we are losing market let's do what the other guys are doing, they are not going to do anything about it.
It's not a priority to meet the w3c standards, it's just a complement if it can be done without much work. On IE7 I only saw the tabs feature and that was it, what else do you expect from a company that has always been about the new look and not the new security feature.
Do it or don't complain.
Unless Bill says ok we are losing market let's do what the other guys are doing, they are not going to do anything about it.
It's not a priority to meet the w3c standards, it's just a complement if it can be done without much work. On IE7 I only saw the tabs feature and that was it, what else do you expect from a company that has always been about the new look and not the new security feature.
<<Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.>>
In other words, neither the new Safari, Mozilla, or FireFox have passed this test either. It remains to be see which browsers are fully compliant once they are released in their final versions. Furthermore, it was not stated *which* tests IE7 will not pass. Simply stated, *none* of these new browsers are compliant as of today.
test in preliminary builds."
Which part of that sentence says it didn't pass the test?
So... it is possible after all.
The difference is that most if not all browsers other than IE actually
make a fair attempt at meeting standards. For MS standards is an
afterthought.... and when someone else does not adopt their
format... the moan about it to no end.
Considering the lag between IE releases and the apparent low priority Microsoft gives it now that there is little strategic threat from a "Netscape", I think the concern is that there won't be an IE 7.5 that meets current standards for years, let alone some of the innovations others will come up with in the meantime.
Camino, Netscape, Opera, Firefox, etc, etc... all are 95+%
compliant. How about IE?
Well, first you have to pick which one, because IE 5, IE 5.5, IE 6
and IE 5.2 on the Mac all have their own set of unique bugs and
non-compliances. So... As a web designer, whenever I design
with CSS, I have to go back and look at the page in IE 5 and fix
those bugs, then IE 5.5 and fix those bugs, etc. etc. All done
with hacks to the standard code (it passes all compliance checks
before the hacks). Now, not only will I have to bugfix for those,
but also for IE 7.
Time spent coding webpage: 1 hour. Time spent hacking the CSS
to fully support IE (with some exceptions - like PNG
transparency which there simply isn't any way to get to work in
IE): 1-4 hours depending on how problematic the bug is.
I shouldn't have to spend ANY time to get the page to look
correct in ANY version of IE. I'm really looking forward to
spending MORE time hacking CSS for another crappy version of
IE.
True, about 90% of the browser market is IE (and a lot of the
user market is compter illiterates). But that doesn't mean we
can't spread the word! When designing professionally I have no
choice but to hack the CSS for IE but I refuse to support IE on
any of my personal sites and have full pages devoted to why you
should be using ANYTHING other than IE. CSS1 is just the tip of
the iceberg. Help spread the word, if it's not professional, don't
support IE. There's even a hack to show text if and only if the
user is browsing with IE. Good for a "Why does this page look all
messed up? Because you're using a broken browser." message.
I was kind of hoping we could be able to put a "upgrade to the
latest version of Internet Explorer for best viewing" message and
help the IE users start weeding out the broken IEs, but it's
looking like that will never happen.
And people wonder why there are M$ bashers out there. Work
professionally in an area where you are constantly banging your
head against the M$ wall for a while and you'll be saying how
much they suck too.
<<Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.>>
In other words, the new versions of Safari, Opera, and FireFox will have passed this test and be fully compliant. It is obvious which browsers are fully compliant once they are released in their final versions and which are not. Furthermore, it was not stated *which* tests IE7 will not pass. Simply stated, all of these browsers next versions are compliant while IE 7 IS NOT AND WILL NOT be.
<<Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.>>
In other words, neither the new Safari, Mozilla, or FireFox have passed this test either. It remains to be see which browsers are fully compliant once they are released in their final versions. Furthermore, it was not stated *which* tests IE7 will not pass. Simply stated, *none* of these new browsers are compliant as of today.
test in preliminary builds."
Which part of that sentence says it didn't pass the test?
So... it is possible after all.
The difference is that most if not all browsers other than IE actually
make a fair attempt at meeting standards. For MS standards is an
afterthought.... and when someone else does not adopt their
format... the moan about it to no end.
Considering the lag between IE releases and the apparent low priority Microsoft gives it now that there is little strategic threat from a "Netscape", I think the concern is that there won't be an IE 7.5 that meets current standards for years, let alone some of the innovations others will come up with in the meantime.
Camino, Netscape, Opera, Firefox, etc, etc... all are 95+%
compliant. How about IE?
Well, first you have to pick which one, because IE 5, IE 5.5, IE 6
and IE 5.2 on the Mac all have their own set of unique bugs and
non-compliances. So... As a web designer, whenever I design
with CSS, I have to go back and look at the page in IE 5 and fix
those bugs, then IE 5.5 and fix those bugs, etc. etc. All done
with hacks to the standard code (it passes all compliance checks
before the hacks). Now, not only will I have to bugfix for those,
but also for IE 7.
Time spent coding webpage: 1 hour. Time spent hacking the CSS
to fully support IE (with some exceptions - like PNG
transparency which there simply isn't any way to get to work in
IE): 1-4 hours depending on how problematic the bug is.
I shouldn't have to spend ANY time to get the page to look
correct in ANY version of IE. I'm really looking forward to
spending MORE time hacking CSS for another crappy version of
IE.
True, about 90% of the browser market is IE (and a lot of the
user market is compter illiterates). But that doesn't mean we
can't spread the word! When designing professionally I have no
choice but to hack the CSS for IE but I refuse to support IE on
any of my personal sites and have full pages devoted to why you
should be using ANYTHING other than IE. CSS1 is just the tip of
the iceberg. Help spread the word, if it's not professional, don't
support IE. There's even a hack to show text if and only if the
user is browsing with IE. Good for a "Why does this page look all
messed up? Because you're using a broken browser." message.
I was kind of hoping we could be able to put a "upgrade to the
latest version of Internet Explorer for best viewing" message and
help the IE users start weeding out the broken IEs, but it's
looking like that will never happen.
And people wonder why there are M$ bashers out there. Work
professionally in an area where you are constantly banging your
head against the M$ wall for a while and you'll be saying how
much they suck too.
<<Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.>>
In other words, the new versions of Safari, Opera, and FireFox will have passed this test and be fully compliant. It is obvious which browsers are fully compliant once they are released in their final versions and which are not. Furthermore, it was not stated *which* tests IE7 will not pass. Simply stated, all of these browsers next versions are compliant while IE 7 IS NOT AND WILL NOT be.
Web designers like myself have been waiting for "the new Internet
Explorer behaves like a browser should!". Unfortunately, we got the
opposite. Personally, I would LOVE to see an "Internet Explorer at
least mostly web standard compliant" headline.
P.S. If you're so hardcore IE, you need to grab this:
http://www.lavasoftusa.com/software/adaware/
Sorry, you're wrong. I care and I'll bet many others do as well.
Why is it that when ANYONE points out what Microsoft IS DOING, ...HAS DONE, ...or has flatly-stated that they [Microsoft] INTEND TO DO, such verifiably-honest people (who are merely pointing out these EASILY-CONFIRMABLE FACTS) are so-frequently called "...bashers"..?
Maybe a better question would be to ask yourself WHY ANYONE would DEFEND a REPEATEDLY-CONVICTED "...illegal-monopoly" which has been found to have "...stolen", "...manipulated", and "...lied", ...time, ...after time, ...after time?
You really should answer THAT question, because another FACT, is that most people who actually work in the industry for any length of time (such as myself, with over twenty-years in the field) quickly are FORCED to realize just how arrogant, dishonest, and incompetent Microsoft truly is.
But then, I am probably just another one of the, PRACTICALLY-COUNTLESS, numbers of "Microsoft-bashers" who, just so happens, CAN actually back-up every NEGATIVE thing said about the company, and its products, ...with FACTS.
"unbiased reviews," and that's the goal of any news site as well.
CNET reports on MS a lot because quite frankly they dwarf any
other technology company. You could accuse CNET of being
Apple bashers too because they rarely report on upcoming
builds of OS X (unlike Vista).
It just so happens that in this instance, I would agree that IE's
situation is lamentable, considering that all the other major
browsers either already pass the test or will very soon. CNET is
expressing the fact that MS has son work to do in this field.
Then when I uninstall the IE upgrade, it removes more than it had installed, causing problems from "file not found" on boot, or an entirely unbootable machine.
I no longer have these problems, because my Macs don't do that, and my windoze machines remain for when I absolutely have to get to some a**hole's web site.
Web designers like myself have been waiting for "the new Internet
Explorer behaves like a browser should!". Unfortunately, we got the
opposite. Personally, I would LOVE to see an "Internet Explorer at
least mostly web standard compliant" headline.
P.S. If you're so hardcore IE, you need to grab this:
http://www.lavasoftusa.com/software/adaware/
Sorry, you're wrong. I care and I'll bet many others do as well.
Why is it that when ANYONE points out what Microsoft IS DOING, ...HAS DONE, ...or has flatly-stated that they [Microsoft] INTEND TO DO, such verifiably-honest people (who are merely pointing out these EASILY-CONFIRMABLE FACTS) are so-frequently called "...bashers"..?
Maybe a better question would be to ask yourself WHY ANYONE would DEFEND a REPEATEDLY-CONVICTED "...illegal-monopoly" which has been found to have "...stolen", "...manipulated", and "...lied", ...time, ...after time, ...after time?
You really should answer THAT question, because another FACT, is that most people who actually work in the industry for any length of time (such as myself, with over twenty-years in the field) quickly are FORCED to realize just how arrogant, dishonest, and incompetent Microsoft truly is.
But then, I am probably just another one of the, PRACTICALLY-COUNTLESS, numbers of "Microsoft-bashers" who, just so happens, CAN actually back-up every NEGATIVE thing said about the company, and its products, ...with FACTS.
"unbiased reviews," and that's the goal of any news site as well.
CNET reports on MS a lot because quite frankly they dwarf any
other technology company. You could accuse CNET of being
Apple bashers too because they rarely report on upcoming
builds of OS X (unlike Vista).
It just so happens that in this instance, I would agree that IE's
situation is lamentable, considering that all the other major
browsers either already pass the test or will very soon. CNET is
expressing the fact that MS has son work to do in this field.
Then when I uninstall the IE upgrade, it removes more than it had installed, causing problems from "file not found" on boot, or an entirely unbootable machine.
I no longer have these problems, because my Macs don't do that, and my windoze machines remain for when I absolutely have to get to some a**hole's web site.
Can anyone ever make an intelligent comment about Microsoft without falling into the cliche hater category?
wants to test it out (Safari fails miserably). The acid2 test
features a ton of stuff that isn't widely supported yet. The acid2
test is the future of standards. Many designers don't use a lot of
CSS2 or CSS3 because the support isn't there completely in most
browsers (although they're obviously making an effort to
incorporate them as more and more are supported with each
release). CSS1 support however, is 99% complete in all browsers
save IE.
Who cares? Web designers and the internet community do.
Creating standards that are widely supported allow us to create
better sites. Pure and simple. When we have to consider that this
feature or that isn't supported by IE, ie 90% of the browser
population, and thus we won't implement it, it hurts everyone.
Not just the IE users.
Ubuntu, Red Hat, Mac, Firefox and OpenOffice are creeping in on Microsoft's territory. Microsoft can't survive for long selling $100-$600 software licenses to go on $100-$1000 of computer hardware in the face of competition that gives their product away. I'm aware that Mac software isn't free, but it's bundled with nicer hardware.
By the time of your post, there were builds of Safari, iCab, and Konqueror that passed the Acid2 test, and iCab even had a public build. Microsoft has yet to release anything that passes, and IE7 is still less compliant than the outdated Firefox 1.5.
Not so intelligent comment about Microsoft:
Internet Explorer 6/7 are good products; it's just that the test is unfair in violating the standards. (I will agree that the test is unfair to violate the standards, but there is still plenty of compliant CSS/HTML that will break down on any version of IE)
Can anyone ever make an intelligent comment about Microsoft without falling into the cliche hater category?
wants to test it out (Safari fails miserably). The acid2 test
features a ton of stuff that isn't widely supported yet. The acid2
test is the future of standards. Many designers don't use a lot of
CSS2 or CSS3 because the support isn't there completely in most
browsers (although they're obviously making an effort to
incorporate them as more and more are supported with each
release). CSS1 support however, is 99% complete in all browsers
save IE.
Who cares? Web designers and the internet community do.
Creating standards that are widely supported allow us to create
better sites. Pure and simple. When we have to consider that this
feature or that isn't supported by IE, ie 90% of the browser
population, and thus we won't implement it, it hurts everyone.
Not just the IE users.
Ubuntu, Red Hat, Mac, Firefox and OpenOffice are creeping in on Microsoft's territory. Microsoft can't survive for long selling $100-$600 software licenses to go on $100-$1000 of computer hardware in the face of competition that gives their product away. I'm aware that Mac software isn't free, but it's bundled with nicer hardware.
By the time of your post, there were builds of Safari, iCab, and Konqueror that passed the Acid2 test, and iCab even had a public build. Microsoft has yet to release anything that passes, and IE7 is still less compliant than the outdated Firefox 1.5.
Not so intelligent comment about Microsoft:
Internet Explorer 6/7 are good products; it's just that the test is unfair in violating the standards. (I will agree that the test is unfair to violate the standards, but there is still plenty of compliant CSS/HTML that will break down on any version of IE)
I don't paticularly feel the need to bash Microsoft over IE 7 since they stated their point better than I could. However I agree with another poster about companies not following standards better. It really does hurt everybody. It cost more money to develope websites that work in the different browsers. It lowers the potential for better websites.
Just because the W3C creates "recomendations" doesn't mean anybody has to use or follow them. We could all just standardize on IE and every browser could use them, but look how long it takes Microsoft to update IE with anything new and worthwhile. They can't even keep the format the same form program to program. This is why following a motivated group like the W3C is a much better idea.
Regardless I figure that IE will probably never fully support W3C standards or anybody elses for that matter, but I do think we will always see browsers that do. They may never knock Microsoft and IE off the top, but life will go on.
I don't paticularly feel the need to bash Microsoft over IE 7 since they stated their point better than I could. However I agree with another poster about companies not following standards better. It really does hurt everybody. It cost more money to develope websites that work in the different browsers. It lowers the potential for better websites.
Just because the W3C creates "recomendations" doesn't mean anybody has to use or follow them. We could all just standardize on IE and every browser could use them, but look how long it takes Microsoft to update IE with anything new and worthwhile. They can't even keep the format the same form program to program. This is why following a motivated group like the W3C is a much better idea.
Regardless I figure that IE will probably never fully support W3C standards or anybody elses for that matter, but I do think we will always see browsers that do. They may never knock Microsoft and IE off the top, but life will go on.
Yes, a balance needs to be struck, but remember that many people just want it simple and want it to work.
For instnace, here is me. I'm a systems administrator and in many cases I hate it when I got zillions of scripts, Java applets and ActiveX stuff popping about all over the place.
I only visit CNET news because I can view and perticipate without letting even one script or applet run! Visiting a site only to have to download this and that and the next-door-neighbours-wife (hmmmm... Maybe not the latter) just puts me off a web site all together.
Put it another way. I don't like http://www.odeon.co.uk/Odeon/home.html but I do like http://www.odeon.co.uk/pls/Odeon/Odeon_text.region_list
I am no way disabled, but navigating through the latter (text version) is a far more pleasent and less stressful experience.
That's my own personal opinion. If you don't like it tough! At the end of the day you can make the most flashy web site about, but if the audience don't like it then you've wasted all that time and effort.
Get the jist?
Wow. What an poorly thought out end user point of view. Never thought about how it might make life easier for the developer, did you? That can benefit the user in a lot of unseen ways, not just by "better features", but maybe by more content and less errors as well. There are a lot of indirect benefits you're ruling out by just saying "I don't like fancy junk, so who cares?"
I agree that a lot of web pages have too much junk on them, but to simply write off better standards support as unimportant just because some designers will use it to add junk seems extreme to me.
Yes, a balance needs to be struck, but remember that many people just want it simple and want it to work.
For instnace, here is me. I'm a systems administrator and in many cases I hate it when I got zillions of scripts, Java applets and ActiveX stuff popping about all over the place.
I only visit CNET news because I can view and perticipate without letting even one script or applet run! Visiting a site only to have to download this and that and the next-door-neighbours-wife (hmmmm... Maybe not the latter) just puts me off a web site all together.
Put it another way. I don't like http://www.odeon.co.uk/Odeon/home.html but I do like http://www.odeon.co.uk/pls/Odeon/Odeon_text.region_list
I am no way disabled, but navigating through the latter (text version) is a far more pleasent and less stressful experience.
That's my own personal opinion. If you don't like it tough! At the end of the day you can make the most flashy web site about, but if the audience don't like it then you've wasted all that time and effort.
Get the jist?
Wow. What an poorly thought out end user point of view. Never thought about how it might make life easier for the developer, did you? That can benefit the user in a lot of unseen ways, not just by "better features", but maybe by more content and less errors as well. There are a lot of indirect benefits you're ruling out by just saying "I don't like fancy junk, so who cares?"
I agree that a lot of web pages have too much junk on them, but to simply write off better standards support as unimportant just because some designers will use it to add junk seems extreme to me.
Lets hope that MS doesn't hold off on the IE 7.1 release for years too and that after they've fixed as much of the security problems they can in this release that the next release is dedicated to fixing IE's deplorable "standards" compliance and not the latest new fad at the Redmond campus which have been the driving force behind earlier IE releases.
Lets hope that MS doesn't hold off on the IE 7.1 release for years too and that after they've fixed as much of the security problems they can in this release that the next release is dedicated to fixing IE's deplorable "standards" compliance and not the latest new fad at the Redmond campus which have been the driving force behind earlier IE releases.
- No way!
- by CharlesJo.com August 2, 2005 10:52 PM PDT
- MS is building proprietary stuff that will give them leverage in the software and related business? OMG.
- Like this Reply to this comment
-
Showing 1 of 2 pages (212 Comments)