MozillaZine

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.


#26 CSS1 difficulty? HA!

by CPT

Monday March 29th, 1999 5:53 PM

You are replying to this message

"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."

Hello, AMAYA!, Hello ARENA!

Do these names mean anything to you?!?! I was surfing with Arena in '96 and it gave me better CSS than Netscape 4. Do you guys get ANY of your information from anyone besides netscape?

Try reading the CSS pages at the W3C (<http://www.w3.org/Style/CSS/> .) It's pretty clear. The only vagueness is where netscape and IE implement things either incorrectly or not at all.

I've done a good bit of web pages CSS and tables, and when there's been a problem, it's almost always on the Netscape side. Mozilla 5 may clear up these problems when it's released (when? end of the year?), but in the here and now it's really easy to beleive that Opera trounces Netscape in CSS (haven't tried Opera myself, but I have tried IE, and it beats Netscape in CSS compliance.)

And yes, being the leader of the pack is a good thing. A lot of people here imply that NS is just as good as the others, since none are 100% compliant. I live in the real world, where few things are 100% and that extra 40% can be nice.

I still think Netscape could have given us a 100% compliant browser with 3.x if they had not tried to shove proprietary crap like Java-script style sheets and LAYER down our throats.