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.]
#238 Forms! And make Gecko standalone
Tuesday July 3rd, 2001 9:22 AM
You are replying to this message
Well, I can't speak about the UI cause I only use the engine together with Galeon. But so I can be a bit more detailed about it. :) To make it short: I would consider the engine to be almost perfect. I can't remember the last time, when I had a problem with website rendering. Of course their is a problem with IE based sites but you can't do anything against it (if you encounter such a problem, email the site authors, not the mozilla team!). There is only one thing, that is REALLY annoying. Macpeep already pointed it out quite well. The HTML forms! To be honest, they suck like hell. At least they improve from release to release, but they still suck. I'm not talking about the design, but about the functionality. Sometimes lines disappear or appear, pasted text isn't pasted where I wanted it to be pasted at, sometimes it does not even work... Or I click the end of a line and the line above is selected instead of the line I clicked... I move the cursor above the end of the text and it jumps to the beginning, but it doesn't work the other way round, so I have to scroll down to the bottom everytime I move one char too far... The more text I write, the worse it becomes... really, this is a major annoynance. If a website element isn't rendered perfectly, that's not a problem. It just doesn't look as well. But if it becomes a pain in the ass to write a larger forum entry (luckily I write this one with Netscape 4 at work), I get really pissed... I mean, a textfield isn't something very complex... you could even use the default textfields of either Gtk or the toolkit you use for the port. You wanted to do it more flexible and now it's crap. :( I really think you shouldn't release a Mozilla 1.0 before all those problems are sorted and fixed. Don't get me wrong, I don't want to offend anyone at Mozilla.org for crreating this HTML forms, I just wanted to tell you what is the last thing that I don't like about the engine. I also think that another focus should be the UI. I just don't care because I never use it and I would even suggest, to seperate the engine from the whole Browser package. Let's gecko have it's own version number, so that a final gecko can be released much earlier. You should also think about merging with projects like Galeon and K-Meleon or at least work with them. Cause I don't see that everyone will prefer a cross plattform application. It's nice to have Mozilla cause it's great, but you should also power those plattform depending great gecko browsers. They just kick ass.
So here are my suggestions in short form:
- Work on HTML forms, I mean usability, not visuality - Release a Gecko 1.0 before Mozilla 1.0. - If Gecko 1.0 is released, you should concentrate your work on the Mozilla shell and make the existence of K-Meleon and Galeon more public. - Release stable versions of every shell and/or Gecko if they are ready (I think at least Galeon is almost ready and only waiting for Mozilla 1.0). And make every release public on Mozilla.org. So if Gecko 1.2 is ready, you would just download that and all your shells would work with it. If a new shell is ready, you just download it and it will work with your Gecko. You get my point? I think that would be much more flexible. Of course there should be always a complete Mozilla package with the newest Mozilla shell and the newest Gecko.
I just wish, that would come true. :-|