Mozilla Most CSS Compliant BrowserWednesday March 8th, 2000According to RichInStyle.com, Mozilla is currently "the best CSS browser available." This doesn't mean that the work is done, however. 110 CSS bugs were found in the November 15 1999 build of Mozilla, compared to the next best CSS implementation (IE5, with 155 bugs). We should see those numbers come down in short order as the Mozilla final release approaches. Note that they were using a milestone from Nov '99 - that must have been M11 or M12? They say they will update frequently, but they don't seem to have done so... On an unrelated note, I wonder if the people at RichInStyle.com could be persuaded to confirm whether these bugs still exist in the latest nightlies and if so, file bugzilla bugs on them. They have obviously done a *lot* of research on exactly what Mozilla breaks, and I'm sure the layout team would love to know about all of these issues. Stuart. it looks like they are filing bugzilla reports against their bugs that don't already have reports. --chris from what the RichInStyle.com owner told in n.p.m.layout it was M11 - but he has downloaded a new nightly this weekend... I noticed many of the bugs they mentioned are not very severe, while others are. Is there any measure of bad the mozilla bugs are compared to the IE ones? The layout engine still has some bugs with normal HTML 4.0, including the frame attribute and the rules attribute of table tags. I'm going to file a bug on these if I can't find them in Bugzilla. I remember a while ago MozillaAdmin wrote an article saying that while IE supports more of HTML 4.0 than Netscape, it's actually *worse* to support more of a standard (but not all of it). So I guess Mozilla is getting worse and worse, then it will reach its lowest point as only one guy is left, and suddently it will soar to perfection. I never really agreed with that reasoning :) I think the exact point was that it's worse to have more HTML 4.0 support but buggy implementation than to have less support but no buggy implementation. I really agree with that reasoning. -Chris What I said was that it's just as bad to support 90% of the spec as 70%. Neither is adequate, because developers will have to work around the 10% or 30% that isn't implemented. However, if half of that 90% implementation is buggy, and the 70% implementation is not buggy, the 70% implementation is better for the standards process (at least it's not partially implemented *and* broken). I tried to view the http://www.zdnn.com with M14 and the CSS positioning is all messed up! Is this becasue of Mozilla or the page's programming? Hmm, looks fine to me (on latest nightly), except that I'm missing a menu on the right. Anyone else having this problem? Yep missing a menu on the right on build 200030215. Funny thing is that if I do a Save As with IE5 and then load the saved .htm file with Moz the menu appears again. Go figure... I know I had the same problem in M13 even though it displays fine in NN4 and IE5. There isn't any CSS positioning in that page, so I'd guess it's a table layout problem not a CSS problem. There are some inline CSS positioning in that page. Can't really compare with NS4 because mozilla gets a slightly different page due to javascript. Moz does get the exact HTML as IE though... or so I thought... It seems that when I do a save as on Nav4, IE5 and Moz I get 3 different html files, go figure... Will investigate further. Basic ...that (out-dated) alpha level software is *less* buggy than a MS Final release software. Excuse me while I swim through this irony. <splash> <splash> <splash> Speak quietly my friend or else someone might note the worst (final realeased) browser. Communicator has an excuse!!! It was released in May of 1997, only about 5 months after CSS1 became a recomendation (Dec 1996) and a year before CSS2 became a recomdation (May 1998). IE5 on the other hand was released only about a year ago, that's over two years after CSS1 and a year after CSS2. Actually, I don't think communicator has an excuse. Personally, I'd like to know what netscape was doing before mozilla. I don't mean to be mean, but obviously not everyone is working on mozilla (ie NGLayout mozilla), because 4.xx versions are getting released with an annoying regularity. Why couldn't somebody have fixed the (slightly) buggy implementations of CSS1 stuff that was obviously screwed up, and could be fixed in a couple months, and stuck that in 4.5 instead of a dorky "What's Related" button? I'd never insult the mozilla team. I think they're doing excellent. I'm just wondering about the rest of Netscape. Actually I agree! I only ment the original Communicator had an excuse. 4.5 and higher should atleast have a repaired version of the original implimentation! I actually remember hearing rumors at one time that Netscape was going to fix some of the style problems in 4.5 (and impliment the hover property) when it was first released. However I guess this was a myth. Either that or Netscape decided to abandon the notion of fixing the old layout engine because Mozilla was making such progress with the new one. The adding up on RichInStyle is very suspect. Somehow 160 listed bugs in IE are counted as 155, while 109 listed bugs in Mozilla counts for 110. I have left a message on the site about this discrepancy... I too would like to see up-to-date figures, but I'd also like decent arithmetic. RichInStyle.com doesn't know s&^*. They're calling "annoying" bugs the same as full-blown severe f-ups. That's not the best part... the best part is (as SomeSmartAss noticed) the browser with the severe f-ups in CSS is the one that isn't being constantly updated and improved because it's not ready for public consumption. I'd say that the compliance should be on a point scale... 1.0 for full, .5 for buggy/annoying, 0 for screwed up/no support. Don't give me that pussy crap about "well, some compliance is just as bad as none." This is the WEB, and stuff moves at WEBSPEED. If everyone waited around until all their products were perfect, we'd still be waiting for OS/2. Flaws are a natural part of manufacturing, standards or not (hell, even the standards are flawed... there's big support for media-types but no ability to make an image a border or any postscript-like vector abilities that paged media should have). Recent builds are doing CSS inheritance very well, unlike NS4.X... (grumble, grumble) NO! Though positioning and so on is very well, there are really annoying bugs like ignoring the background-color, -image, -position. And this hasn't changed since I had the first milestone - I think M10 or M9. Until this hasn't fixed it can be only 3 css-bugs and the css implemention is still s..! My homepage http://www.simifilm.ch/ is fully XHTML and CSS2 compliant according to the validators on w3.org. When loaded with mozilla, I only get an empty screen. Does mozilla not support XHTML? Am not an expert, but if I were to guess, I'd probably say it was the CSS2. Remember that Mozilla only partially supports CSS2, and they are not garunteeing that it'll even be in the beta release (even though part of it is likely to be in there). Shawn =) I don't think that CSS2 is the problem. I only use very basic commands which are also part of CSS1... Any ideas? last I checked. Of course I haven't touched CSS in 6 months so maybe something's changed. (Mozilla's "failure" to support border %'s is counted as a "bug"....) I checked back today and found that Mozilla now has 104 bugs (6 less than before), while IE5 has climbed to 160 bugs. |