Opera Now Most Compliant Browser, According to WebReview
Friday March 26th, 1999
CNet reports that WebReview's latest assessment of CSS1 compliance in release browsers puts Opera on top with 78%, followed by IE4 at 70.2% and Nav4 at 38.8%. Neither the M3 release of Mozilla or IE5 were assessed in the recent tally.
Contrary to the opinion of the study's author, Eric Meyer, who stated that Opera was "really very impressive, especially given its relative youth", a buggy 78% implementation hardly seems worth touting. As I've stated before on these pages, a browser that has is 78% compliant and buggy is as useful as a 10% compliant (but bug-free) browser. In fact, the 10% compliant browser is the better option, because no workaround code is required for implementation. However, the only browser that should garner any praise is the one that is 100% compliant, and bug-free in its implementation.
In addition, an interesting statement from the WSP that appeared in the CNet article is worth mentioning.
"The uneven deployment of CSS1 in major Web browsers over the last two years has caused Web authors great frustration and expense, and has won CSS an undeservedly obscure and difficult reputation"
From my experience watching the progress of Mozilla's CSS1 implementation, it seems that CSS's reputation for being difficult is deserved. Developers have had to search the CSS2 definition to clear up vagaries in the CSS1 definition. There is no reference CSS implementation *anywhere*, so developers are essentially guinea pigs and have to not only implement CSS1, but spend time and money working through all the inconsistencies that were not addressed by a reference implementation. It doesn't seem that the uneven deployment of CSS implementations has caused CSS1's reputation. If anything, CSS1's vagueness has had the direct result of limiting its adoption.
#16 Re:Opera Now Most Compliant Browser, According to
Saturday March 27th, 1999 9:04 PM
You are replying to this message
You stated, "What you're saying is obviously that IE's 70 or whatever % is a higher percentage than Netscape's 30%, but that Netscape's 30% is handled perfectly and IE's 70% is botched."
No, I never stated that, and never even *implied* that. I really don't know how you even got that impression. My comparison between a buggy 80% implementation and a 10% perfect implementation was *hypothetical*.
I never stated that Netscape's implementation was 10% and perfect. That was a misunderstanding on your part. As I stated in my last post, *all* of the release browsers up to this point are buggy. Netscape's browser is no exception.
The point I was trying to make is that a buggy implementation is essentially worthless. That means that the CSS1 implementations in all of the browsers up to this point is essentially useless, except for experimentation and development in restricted environments (like intranets).
If a browser came out tomorrow with a 10% implementation that was perfect, it would be more useful in the long run than anything we've had so far.
I hope this clears this issue up.