Slashdot Mirror
Planning For Mozilla 2.0
wikinerd writes "The MozillaWiki maintains a number of pages on Mozilla 2.0 which reveals lots of possible new features of the popular browser. What does your wishlist include about Mozilla 2.0, and how has the release of Firefox affected your use of Mozilla?"
What's with Mozilla 1.4, er, I mean 1.5, er, I mean 1.6, er, I mean 1.7 being the Last Release Ever?
My wish is that Mozilla properly render Slashdot. What an embarassment! Someone even went so far as to make a Mozilla plugin that fixed the Slashdot rendering bug! I mean, c'mon people, you'd think that Mozilla would properly render Mozilla's biggest supporter.
"If at first you don't succeed, lower your standards."
So I always used Moz. Personally I think the best change for Moz would be to make it less bloated, and make it totally modular. Basically make it so you can strip away most of the program and turn it into something closely resembling Firefox if you so choose.
Plus, Firefox seems quicker and more stable to me since I have been using both.
Mozilla and Firefox will merge into one super borwser....MoFox... or perhaps FireZilla
I would like to see something like what opera has with web page magnification. Its on firefox too but you cant make images any bigger then they already are like you can with opera. But i still like FF better.
When I read about the evils of drinking, I gave up... reading.-Henny Youngman
Ditto. Mozilla was bloated anyway. If you wanted its full features, you could take advantage of it, but I preferred the lighter Firefox, anyway.
The features I wanted are already found in Firefox (i.e., tabbed browsing, popup blocker, themes & extensions). I just don't need Mozilla any more.
Mercy was given to me by Christ...I must give the same to others.
This has been fixed in the trunk for a long time (but not the branch Firefox 1.0 comes from), and will be in Firefox 1.1, whether Mozilla increments to 2.0 or not.
Bug 217527
Bug 264913
If you really, really need a fix now, visit this URL and download one of the nightlies from the trunk [fair warning - some nightlies have some annoying bugs in them, but generally, are pretty good]. It works just fine there, but I'm told requires too many changes to backport into the ff1/mozilla whatever branch.
I would like to see a build in page validator.
There is a lot of badly coded web pages out there.
It might take a rewrite of gecko by I think it is wroth it.
The normal web based validators really don't cut it
when your developing dynamic cgi scripts.
I still remember the day when I tried running two separate instances of Mozilla on the same Windows machine. Neither Google nor the forums helped. Luckily I can still read C++.
Open source should mean you can look into the source if you want to, not that you have to look into the source every time you try something non trivial.
Shameless advertising post!
I've been working on a project to be able to manage Firefox with Group Policies, but I may be extending it to cover Mozilla as well. Its a bit rough and ready, and needs a good deal of optimisation but importantly, it works and there's a number of people using it successfully...
http://spaces.msn.com/members/in-cider/
Though its not directly related to the Mozilla Suite (sorry, I tried to RTFA, but its down) my biggest wish is to see the Gecko Rendering Engine (GRE) finally split from the Mozilla/Firefox/et al code base. This seems to have completely dropped off the road map despite being discussed for months (years?).
The idea of running the GRE as a service (started at boot) and then simply launching the frontends for the various Mozilla apps (in my case, Firefox and possibly Thunderbird) appeals to me immensely.
I value "snapiness" greatly when it comes to my web browser and email apps. Having to run multiple instances of the same rendering engine is a bit of a downer IMHO. (Yes, I realise there are some benefits. Yes, I realise we all tend to have ample computing power.)
[A graphical history record]
That, combined with a history TREE instead of a linear, self-overwriting history (go back 3 pages and click another link -- those 3 pages will drop out of the history). That's what I wish for.
And for the troll/poster thinking this is for prn -- nope, it's for retrieving pages with 'unknown' URLs. Surfing page to page, one is likely to not read the URL or page title, but to recognize the page body.
"Good news, everyone!"
Of course, some of the above may alreay be planned but as I can't get on mozilla's web site, I can't check.... Maybe it was slashdotted?
One of Mozilla's greatest strengths is not as just a web-browser but as a cross-platform application development platform.
Just try playing around with XUL a little. It's surprising what it can do. I'm just starting out with it, but having worked my way through MFC, QT, TCL/TK, WTL, GTK++, FLTK, wxWidgets etc. etc. in search of the One True UI Library, I'm liking what I've seen so far.
Use standard GNU autoconf for the builds. Get rid of all the code that says things like "#ifdef HPUX ... then do this and that and this and that because HP's C++ compiler (no, not that one, the other one... and that specific version, too!) can't make a negative zero or some such tomfoolery ... #endif". When I try to build Firefox 1.0 (One Point Fucking Oh!) on HP-UX 10.20 it falls over and dies because I'm not using HP's C++ compiler... nor the other one... and especially not that version... I'm using gcc! What do you think I am, an idiot? Why would I use anything but gcc/g++?
But it's worse than that. A few simple platform-checking #ifdefs could be fixed, the code converted into autoconf checks and replaced with HAS_FOO macros... but no. The build tree isn't even a tree -- it's a fucking forest! There are like 17 different build trees, each one gnarly and moss-covered and subtly (or not so subtly) different from the next, all plastered together into one shambling mass of code. Some of the sub-trees hard code ld -foo -bar -ZxCvB commands instead of invoking $(CXX) to be the linker. Some of them hard code cc as the compiler instead of using $(CC). I shit you not. Oh, and you can't type "make" in a sub-trees to build just that sub-tree. You have to start all over from the top level. After a few days, I gave up.
It's bad, folks. Really, really bad.
I'd be embarrassed to release something like that as a 1.0 version. 0.6 alpha 2? Sure thing, no problem. But 1.0 is supposed to be finished.
P.S.: your "Firefox" code still unpacks itself in a directory named "mozilla". Not "mozilla-1.7" or "firefox-1.0" either... just plain "mozilla". It looks like a CVS snapshot to me.