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.]
#45 Wrong, wrong, wrong!!
Wednesday June 27th, 2001 9:55 AM
You are replying to this message
Oh God please help us! No! A more complete CSS2 implementation is not what Mozilla needs at this point. It also doesn't need modularization or complete HTML 4 support. Nor does it need XSLT, SVG and other stuff like that.
One of the few posts that got it right, IMHO, is the first one in this thread by NilsE. What Mozilla really needs is to polish the end user experience. This includes things like 100% consistent user interface from installation, through the browser and all the way into the last dialog. It includes things like pixel precise margins, borders, layout, icons, no typos... It includes not just looks but feel. If a tree node takes one click in bookmarks to expand, it should take one click in every other tree in the app to expand. The upper-right edge of each tree or table should be identical. Clicking on form fields should not resize them and reflow the page. Text should be properly aligned inside form fields. Etc. etc. etc..
These kinds of things (in one word "polish") is what is needed in order for people to get the feeling that they are dealing with a good quality product. The fact that Netscape 6 shipped without this polish surprised me majorly. I can understand things like crashes or non-complete CSS2 implementations.. That's like selling a car with slightly less horsepower than planned. But lack of polish is like selling a car with scratches in the paint.
We need to get the scratches out of Mozilla!