On Sunday 21 October 2001 21:49, Mike Jaques wrote: | I would also ask that all 4xp bugs get a look prior to 1.0 declaration. | Mozilla 1.0 and whatever Netscape release that springs forth from it | should be able to do EVERYTHING 4.x does so we can label it as such and use | it as a reason for everyone (enterprise users mostly) to finally give up | their entiquated 4.x browser and adopt Mozilla 1.0/Netscape 6.x | | I'm sure a few of the below bugs probably include 4xp keywords, but last | i knew there was a bunch of them left, and IMHO they should all be | vanquished prior to 1.0 classification.
There are, basically, 2 possibilities: 1) to be compatible with Netscape 4.7, and bring forward a lot of efforts fixing compatibility issues (with *legacy* product) 2) to be compatible with W3C standards (CSS/DOM) I prefer second option :-) As far as I have seen on Bugzilla, there are only around 500 CSS bugs targeted for Mozilla 1.0 release. Taking into consideration remaining timeframe, I think it's very much possible to fix these 500 bugs. (it's just about 80 bugs per month) | Mike J | | "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. | > * {display: marker}, {display: compact}, {display: run-in} * context generation * display: inline-block from CSS3 (as it's already implemented in MS IE6 and MacIE5) * CSS in TABLEs (so, it's CSS2 but needs to be implemented) | > Here are the bugs I have shortlisted, in no particular order, and the | > reasons why: | > | > 98252 New W3C CSS page hurts Mozilla | > We really should be usable on the W3C CSS page. this should be top priority, no questions | > | > 78094 Floats Are Broken | > This is a very important CSS1 area. Indeed. | > | > 97726 line-height&font-size | > Serious W3C CSS1 test suite failure. I vote for this, too. | > | > 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. There is nothing more important than compatibility with W3C standards. If Mozilla 1.0 released without completed CSS1 (and taking into consideration launch time, Mar.2002 - CSS2), it will be a big failure. As I have mentioned, there are only 500 CSS bugs targeted at Mozilla 1.0 release. Most of them are quite valid and sound. | > | > -- | > Ian Hickson -- Vadim Plessky http://kde2.newmail.ru (English) 33 Window Decorations and 6 Widget Styles for KDE http://kde2.newmail.ru/kde_themes.html KDE mini-Themes http://kde2.newmail.ru/themes/
