MozillaZine

Full Article Attached Towards Mozilla 1.0

Tuesday June 26th, 2001

Gervase Markham recently posted his feelings on what a 1.0 release of Mozilla would be. Gerv has sent us the follow-up to that posting, including much of the feedback he received. To read it, click the full article link. Once you have read through it, we welcome you to post your feelings on what you think a 1.0 release would have. [As Gerv says, please don't post your favorite list of bugs, only the criteria for choosing what bugs to fix.]


#80 Criteria

by tny

Wednesday June 27th, 2001 3:17 PM

You are replying to this message

1. Full support for HTML4, DOM0, DOM1, CSS1. I wish we could wait for genuine XSLT usability (my XML/XSLT pairs don't work in Mozilla, though they do tranform fine in three other engines), but I think it will take longer to get that up to speed that Mozilla has time to spare, and from what I remember XSLT and CSS2 were not promised. This is something IE is mediocre at (though the Mac version is better), and will give Moz an opportunity to shine. Composer should not use deprecated HTML elements.

2. Internationalization: Greek, Hebrew, and Arabic are also important, especially as second languages. Remember that some of the documents browsers will be used for will be in the user's second or third language. This is something IE is very good at, raising the bar a bit for Moz.

3. Stability: I should be able to go to the top sites, using the most widespread technologies (Java, Flash, QT & RealMedia, etc.), and expect not to crash. Ok, maybe I can't reliably expect to plug in some wild 3 party viewer that no one else has even heard of; but the major plugins should work reliably every time; CSS1 and HTML pages that are valid should never crash the browser, and the most common coding errors in HTML should be gracefully handled.

4. Encryption/E-Commerce, Security. I should be able to use Mozilla anywhere I can use IE to buy anything, and know that I'm getting commercial-strength encryption.

5. Un-4-ication. I should never have to use Netscape 4.x because what I want to do can't be done in a Mozilla browser.

6. Usability: this is mostly what folks have been calling polish: the UI should always behave consistently: there should be no reason why I'd notice a rendering bug in the UI.

7. Documentation. There need to be three different levels of complete documentation: the help files have to be complete, explaining every feature exposed to the general user - 'cause face it, a lot of users will be using Mozilla, even if it is intended as a developer product. Also, how one hooks things into browser and composer functionality through XUL and JavaScript should be better documented, so it's easier to learn how to extend the browser. And of course, the more general "this is how the code works" documentation has to be done.

Hope this is of some use.