Actually, this summs up pretty much what I want... http://www.e.kth.se/~e97_jsi/moz1.mp3
: ) / Sicking "Ian Hickson" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Mozilla 1.0 is coming soon, and mozilla.org have asked me to try to list > what standards compliance bugs should be highlighted in that context. As > this is an open project, I am asking for your help in doing this. > > The importance criteria are apparently: > > - bugs which currently cause problems on the web, or will do so in the > near future > - bugs that might come back to bite us later if we don't fix them > > Unfortunately that covers a good 4000+ bugs, so we will have to narrow > them down a little if mozilla.org is to hit the target release date for > 1.0 (sometime in March 2002) with the ability to say that lots of > standards compliance bugs were fixed. > > Here are the bugs I have shortlisted, in no particular order, and the > reasons why: > > 41924 Change how layout handles broken images (alt text) > People keep complaining about this. > > 104035 Should use system cursor for 'pointer' (hand) on Windows > My flat mates say this is the one thing blocking their use of > Mozilla. > > 1777 'text-decoration' should not be drawn by children (underline) > This is one of the few major remaining CSS1 bugs. > > 5693 :hover should be hierarchical > This has been coming back to bite us for years. > > 98252 New W3C CSS page hurts Mozilla > We really should be usable on the W3C CSS page. > > 13213 events don't reach elements to top or left of view > This currently causes lots of problems on the web. > > 35984 Undeclared entities are ignored when external DTD not found > XML error handling is critical to the use of XML. > > 3935 mozilla-native psuedo classes and properties should be marked as such > This is hugely important to the future of the web. > > 86276 split to containing block is not working for XML > A major bug in XML-in-CSS styling. > > 34297 form controls with style="display: none;" unsuccessful in Mozilla > This is another bug that keeps biting people. > > 72360 Crash caused by attempting to create a circular frame list in tables > This would block the use of CSS tables due to it crashing Mozilla. > > 78094 Floats Are Broken > This is a very important CSS1 area. > > 97726 line-height&font-size > Serious W3C CSS1 test suite failure. > > 15405 Root element is stretching vertically to fit the viewport > Another serious CSS1 bug. > > 46918 line-breaking bug caused by +ve margin-right on inline elements > 3490 line-breaking bug caused by -ve margin-right on inline elements > A couple of serious CSS1 bugs very visible on the W3C test suite. > > There are plenty more important bugs -- but I'd like your help to decide > which are the most important. Please reply to this thread (and cc me) > giving a bug number and summary and explaining why your bug needs to be > fixed to match the two importance criteria. (Please keep your replies to > the n.p.mozilla.layout newsgroup.) > > Note that Gerv has told me that this is not a list of "blockers" -- 1.0 > might well ship with none of these bugs fixed. It's just supposed to be > an indicator of what bugs mozilla.org would _like_ us to work on. > > -- > Ian Hickson > >
