Mozilla 0.9.4 Released
asa writes: "Lots of bug fixes (1,467 at last count) since 0.9.3 including the ability to disable the JavaScript window.open() method during page load and unload events. You can find more information on what's new at the release notes and mozillaZine."
I've got the new release mirrored at ftp://nerf-herder.net/pub/mozilla
-Peter
Disabling window.open has been around for a couple of releases now, it's just not the most straightforward thing to enable. I was most pleased to find that hitting enter after filling in a form will actually submit a request everyplace I tried it, assuming that's the intent of the form (i.e. a search engine). This seemed to be a hit-or-miss thing in previous releases.
Interested in open source engine management for your Subaru?
Hopefully these things have gotten better, it is quite annoying when the browser crashes
If Mozilla is going to be able to compete with the major browsers, it (IMHO) has to be a lot more stable. I can cope with a page being rendered badly, but not with a browser crash. IE is still a lot more stable. Or.. perhaps it is just bad Java Runtime integration ?
Thanks anyway Mozilla team, i'm off to the download zone
Probable impossibilities are to be preferred to improbable possibilities.
Aristotele
Wow, what a great release! I think that 0.9.3 really is a key step in the right direction for 1.0. See http://www.mozilla.org/roadmap.html for more details on the roadmap and plans for 1.0.
Also, as a mozilla developer, I would like to thank all those who have joined the project recently and done something to help. Even if you cannot code, there is still lots that you can do. I urge you to download 0.9.4 or even better, a nightly build, and to look at http://www.mozilla.org/start, http://www.mozilla.org/qa/help, and http://www.mozilla.org/get-involved.html. There are many things that you can do to help which will help get 1.0 out the door sooner and better.
No POPUPS whatsoever:
user_pref("capability.policy.default.Window.open"
But...if some sites need popups, make a zone for them like this:
user_pref("capability.policy.strict.sites", "http://www.evil.org http://www.annoying.com");
user_pref("capability.policy.strict.Window.alert"
user_pref("capability.policy.strict.Window.confir
user_pref("capability.policy.strict.Window.prompt
It is very cool, and there is a lot of scripting and other trickery you can do with these prefrences.
-David
# Hack the planet, it's important.
Actually, it goes 0.9.9, 0.9.10, 0.9.11,...
Gerv
I've been using Mozilla's daily builds as my standard browser since M18 and as my email client since 0.8 and I've got to say that I love it - yes, it is a memory hog but I have more than enough memory to give a fsck.
I've been trying to evangelize the users from my work place into using Mozilla since 0.9.2 and so far I've managed to get 10 out of 90 to switch (from Netscape 4.75 of course, IE is a no-no acording to company security policy).
Way to go Mozilla Team - it gets better every single day, congratulations!
All browsers' default homepage should read: Don't Panic...
Also make Mozilla reply as "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)".
That's a bit silly, isn't it? You'll get served IE DOM content, and it won't render correctly.
Gerv
Lynx is probably faster still. But it doesn't mean you necessarily want to use it. This is not an excuse (Mozilla should be faster than it is), it's just an observation.
Gerv
It comes in handy on a few sites, and the option is easy to toggle. In fact most sites that do bitch about a non-ie browser work just fine after I fake the user-agent.
Also make Mozilla reply as "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)".
Please don't do this. It just makes life harder on web designers. How can we optimize our HTML code to render correctly in your browser, if you lie to us about what browser you're using?
Of course, there may be a few cases where it's necessary to do this temporarily, on a per-site basis, but please don't do this long-term.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I've been using Moz daily for almost a year now for both web and mail. I downloaded a daily a couple days ago and it's getting better all the time. The most notable improvement: The mailer isn't a time-sink like it used to be. Even in 0.9.3 it would take me upwards of 1 or even 2 minutes to click "new msg", put in 3 recip addrs, type a subject line and then start writing the body. Luckily I only write about 3 emails a week...
324006
> much slower than the older versions of Netscape
Because it's still beta-quality code? There are many performance issues currently being worked on. Also, some things that NS4 does quickly (eg style resolution) take a lot more time to do _right_.
Now, in the inevitable war between the annoying ad companies and the poor downtrodden browser users we'll get no more popups, but click-thrus or something even more insidious instead.
/. crowd decries the use of Smart Tags (because they change content) but is more than happy to change content they DON'T like (popups and banner ads). Do I smell a note of hypocrisy here?
I can't wait for "This site cannot be viewed without the EvilPopupsAndPersonalInfoCollector plugin installed".
Don't get me wrong, this is a good interim effort but web advertising is going to continue.
<obtroll>
I also find it interesting that the
</obtroll>
Fear: When you see B8 00 4C CD 21 and know what it means
In my mind, I don't think of Mozilla or Netscape 6.x to be an upgrade to Netscape 4.x, I think of it as a completely different product. Any time that you rewrite 100% of the product, you can expect the new version to be slower, more infested with bugs, and just "feel" worse than the older version which has been tended for many years.
/. without permission from the people involved, but someone at Netscape (d. hy.) did a lot of work on page loading and a new contributor did a lot of proformence work as well recently (jes.). Mail/news also uses the widget in the folder-paine, which has great speed increases as well.
However, if Netscape decided not to do the 5.0 rewrite, disaster would be the only end. The old code was not mantainible and doesn't allow for the powerful new features and embedding that seamonkey allows for.
Speed is something that is being worked on and is significantly better than before. I won't mention full names here on
So we are trying the best we can. As always, patches are welcome.
Zach
See this newsgroup post for details.
Of course...they are reaching 1.0 exponentially :-)
Links is text based, renders frames, and has HTTP 1.1/keepalive support, color. It supports the mouse in terminals too, so you can just click links.
I perfer links over lynx.
Netscape 4.7 is older, WEAKER, of course its going to be faster.
Think about it.. the most powerful browser cannot be the fastest browser.
If you use Linux, please help development of Autopac
Konqueror does a much better job than Netscape
4.x of doing styles right, and it's a lot faster
than Mozilla. I wish the Mozilla people well,
but it's simply false to claim that the slowness
is required for a correct implementation.
Everyone who complains about speed doesnt know anything about how computers work.
New software is bigger, more powerful, and NEEDS a more powerful computer, RAM IS CHEAP, dont tell me Mozilla uses too much ram when you can buy a gig of ram for under $200.
Get a faster harddrive, if mozilla is slow you are most likely using cheap IDE crap.
Now, if you have a modern computer THEN you may use modern browsers and modern software, if you have a computer which was made before Netscape 4.7 was released, then you should be using netscape 4.7, your computer will never be powerful enough to run mozilla.
If you use Linux, please help development of Autopac
We'd be very interested to hear of pages Konqueror gets right, and Mozilla gets wrong. Please file bugs in Bugzilla here, and then quote the bug numbers. We'll get right on it.
Gerv
If you travel over to one of the following pages on mozilla.org, you can learn all that you can do to get involved. Confirming the unconfirmed (from page number 3 below) is a great way to get involved, doesn't take much time, and is of a big help when all the many bugs come in after a big release like this.
Come on already.... lets get a spell checker folded into the email client. I need ALL the help I can get. I tried hacking the 6.1 checker in to the last build, but no luck. Is there any word on when - world acording to me - one of the most basic things about an email client will be included?
+++ UGUCAUCGUAUUUCU
In Windows NT/2000, users can set in the mouse preferences for the mouse to automagically move to the default button in dialog boxes and alerts. However, Mozilla doesn't currently cooperate with this.
:). Or, if you aren't inclined to programming, you can also vote for the bug (of course, you'll need a free Bugzilla account to vote).
The bug has keyword "helpwanted", so if you know how to accomplish this functionality, please speak up
Alex Bischoff
HTML/CSS coder for hire
Netscape has a proprietary spell-checker which it ships. No-one has yet found time to write an open-source one. Obviously, no-one at Netscape would spend time doing it, and external contributors are busy on other things. The usual trick is to use a build close to a Netscape release and install their spellchecker.
It would make a good CS project for someone. Fuzzy logic matching isn't all that hard. The UI is open source, it's just the back end that's currently proprietary.
If you are interested, mail me and I'll point you in the right direction.
Gerv
Changeable user agents is bug 46029. Feel free to vote for the bug if that issue is important to you.
Alex Bischoff
HTML/CSS coder for hire
Would you mind posting the DTD for JavaScript?
Oops! I nearly forgot, scripting languages don't have DTDs!
And sure, some backwards people would prefer no scripts in their HTML, but the rest of us actually prefer the design flexibility... and it's just a fact of life that browsers have different, mutually incompatable bugs in their implementations, as well as "additional features."
-n00m
I used netscapes 6 spellcheck.xpi with an early version of mozilla and it wored fine. It doesnt work with 0.9.4 (just tried) hopefully someone fixes this soon.
The bug for getting a spell checker into Mozilla is bug 56301. If you can help out with the effort, that would be fantastic, as the bug is somewhat stalled at the moment.
It used to be that you could install Netscape's spellchecker, but that is no longer supported.
PS Gerv: This message isn't directed at you, but primarily at the parent post to your post.
Alex Bischoff
HTML/CSS coder for hire
They don't?
It's hard to be religious when certain people are never incinerated by bolts of lightning.
Thank you very much for trying Mozilla and reporting bugs. However, this is not the right place to report a bug as there is no way to track it here with the hundreds of other comments.
e r.html and follow the instructions there to report bugs. Espically, please please please search for duplicates before you file a bug. After a release, the number of bugs filed jumps by huge amounts and many of these are duplicates. Please let us who are working on Mozilla work on code and not weeding out duplicate bugs.
Please travel over to http://www.mozilla.org/quality/help/bugzilla-help
Thanks
Are they planning on keeping this awful behavoir?
:-) If you don't like it, and it makes it into Netscape 6.whatever'snext, then if you haven't filed a bug you've only got yourself to blame.
Best way to find out is file a bug and see
Gerv
The reason moz/nscp6 is slower than 4.x is that the entire user interface is built out of XML, CSS, and javascript (something collectively referred to as XPFE). This approach ensures that there's as little platform-specific code as possible, making mozilla available on a wide number of platforms that simply wouldn't have been plausible if everything was being done natively. It's been said many times that if not for XPFE, there wouldn't have been versions for anything but Windows and possibly Macintosh.
The good news is that UI responsiveness improves with each release, and I fully expect it to equal 4.x in time. However, I've read that GTK is a bottleneck of some sort, so that's why Windows has a performance advantage over *nix.
but that is no longer supported
;-)
Well, the 6.1 spellchecker is not supported with current builds. But if you wait for the next Netscape release, the spellchecker will work with those builds and all following builds (until we break it again
Gerv
Mozilla 0.9.4 still feels sluggish on my machine, a 1.1 GHz T-Bird w/ 512 MB of PC133. It feels sluggish under both Linux and Windows. Yet the GIMP and Photoshop (not to menton my games) never felt so fast. If I can shuffle AutoCAD projects with 5+ million elements with ease, I should at least be able to have a complete, yet zippy, web browser.
Granted, newer software is generally larger and more capable, and thus often requires more cpu cycles to do its job. Yet Mosaic and early (pre 2.0) versions of Netscape ran fine on my Sun SPARCstation 10 so many years ago. With advances in coding and cache techniques, not to mention the abilities of modern compilers and the speculative processes doen in the modern cpu -- why must a modern web browser run so slow??
My SPARCstation 10 had a single 50 MHz SPARC processor and 32 MB of rather slow ram. Has Mozilla gotten so far out of hand that even the latest 1+ GHz wizbang PC can't even handle it? Is Mozilla actually more demanding than my Maya rendering daemon??
I say finish up Mozilla. Release 1.0 'when it's done'. Then go back to the drawing board and start over. Bring in some of the old school coders, the folks that didn't have 4+ GFLOPS CPUs. Bring in the old browser folks... Marc Andressen, JWZ, etc.
Sure, Mozilla will be fine by next year when it hits 1.0 and when we all have 2.0 GHz PCs. Browsing will be great at that point. But I pitty the next advance in browsing, because Mozilla 2.0 will certainly bring back the slowness. It is time to start over and do it right.
I've been using Netscape Communicator 4.72 for the last X years. Why? I have over 82000 email messages that I have kept! I do not want the hassle of moving over to Outlook or some other platform for email - lots of filters to set up, _lots_ of folders to set up, and many many thousands of messages to transfer. So I've been waiting for Mozilla to mature. I have tried it a few times over the last two years - and always it has not quite made the cut. In particular, importing the huge number of messages and folders has been a real hassle (often crashing). I'm getting close to switching. This release seems much better. We'll see...
"Blade Runner" the Comic Noir, "Akira" the Film
Helping with organizational effectiveness is our job.
That won't be fixed. You'll have to wait until the next time Netscape releases a spellchecker.
Gerv
I can't figure out to use the new feature for blocking window.open() attached to OnLoad or onUnLoad in the latest build for Win32. Can anyone point out where it is?
I have to say I'm am extremely impressed with the latest releases of mozilla, there has again been a very very nice speed jump.
As a submitter of bugs, it's good to see them getting cleaned up, at this point it's better than many browsers that call themselves 3, 4, 5, 6, 7... whatever.
Stability is getting really good, I haven't been able to crash the latest 0.9.3 nightlies or 0.9.4, even with java, javascript, and flash.
Really excellent work, my thanks goes out to everyone who has helped with Mozilla.
Sticking feathers up your butt does not make you a chicken - Tyler Durden
(there goes my option of opening in a new window)
That's bug 55696.
Gerv
How about not optimizing your page code instead? Just write HTML 4.01 or XHTML 1.0 or CSS1/CSS2 or Javascript 1.2 or whatever according to the standards ( see www.w3c.org for all of them ) and make life easy on all of us. I find it annoying to go to a site and see "Sorry, Netscape 6.x isn't supported.", flip the user-agent string to IE5.5 and discover that the site renders perfectly in Mozilla 0.9.recent. To me it says that the site doesn't care what customers it annoys and that the designer doesn't know how to create HTML pages.
Yep, you can prevent sites from resizing windows as well. It's possible in roughly the same way as popups, with the same level of control. You'd need to ask in the newsgroups exactly how to do it.
Gerv
Menu item spacing is larger for Bookmarks Menu. Vote for this bug.
"There ought to be limits to freedom"
The obvious workaround for advertisers desparate to be as annoying as possible:
var w = window.open(...);
if(w == null)
window.location = "popups_required.html";
redirecting you to a message telling you that you need to enable popups to use the site
There's 10 types of people in this world, those who understand binary and those who don't.
This seems to have been a re-occuring problem among all of the releases, but even worse with .94 (.93 seemed to be getting better). Here are my specs : 1.2 ghz athlon w/ 266 fsb, 266MB PC133, gf2 ultra, sblive 5.1...)
I started mozilla having 136 MB with the buffers & cached memory. After about an hour or so of watching realplayer videos in cnn & abc and going to various sites I had only 85 MB free with buffers & cached memory included. I noticed a very aparent slowdown in the way programs loaded. I closed the window with realplayer with no ram gain. I then clozed mozilla. and my free memory went back up to 135 or so.
This may be caused by the fact that I have 4-5 windows open at once. I later tried using the "flush memory" option which only freed up about 5-10MB. The older versions seemed to have much less of this problem, but it was still noticeable. I use opera 5.05TP1 and it not only loads in a second or two, but is much faster at loading web pages and allows you to have up to 10 or more pages open at once in one opera window. This is quite nice for the way I browse. Unfortunately It does not have real player support, but id does have java & flash suport.
Rendering pages is extremely FAST but creating windows is SLOW. The main hitch I have right now is on new window creation (which takes a long time to do). For example on a test page that uses javascript to open and close 75 windows one at a time (see the super simple code at this URL and either copy and make you own test or click on the link on that page):
http://206.191.52.79/MozTester/pagebanger.html
On a P233 running Linux I get the following (you'll likely want to try this on a faster machine - it's the relative comparisons that are interesting).
* Netscape 4.7.* takes about a minute
* Opera takes about 15 seconds
* Mozilla takes about 5 minutes !! (actually I stopped timing it's so slow)
* KFM/Konqueror ?? (old version doesn't work try it with KDE 2.0)
* Galeon ??? (not timed recently - the sort of more "native" GTK GUI might be faster??)
* Embedded Moz etc.
* Other browsers??
On MS Windows the Mozilla GUI is likely faster (haven't tested) and IE of course is very fast
Some of the slowness is due to the server so I engourage you to create your own javascript tests that just openm and close blank windows or something
This behavior is not optional because there is no API to request a cached load at the moment. This API is being added. It is not yet in 0.9.4. As soon as it's added, I'll change the view source code to use this API and the problem will be gone. There is an existing patch for "save" that with a few small changes will start working then too.
Oh, and aspell/ispell is Unix-only,no?
It's amazing how much less irritating browsing the web is since I disabled popups and animation in Mozilla.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
> 4.x of doing styles right
True. That's really not saying much. I've tried Konqueror and it's style and DOM support is pretty crappy as of last month...
If you have 192M of RAM on your laptop and you still feel that it's slow, the problem isn't due to lack of RAM. I've used earlier releases on machines with only 64M and it worked fine.
the good ground has been paved over by suicidal maniacs
> Anyone else notice that this release's tag now
> automatically works as a submit button
What do you mean by that? Are you referring to the <button> element? If so, a <button> with no type specified is supposed to be of type "submit" per the HTML4 spec. If you want it to be type="button", say so in the tag.
The definition of <button>. Of particular interest:
type = submit|button|reset [CI]
This attribute declares the type of the
button. Possible values:
* submit: Creates a submit button. This is
the default value.
Mozilla's just finally gotten around to what is _very_ plain in the spec. use type="button" if you want it to be just a button.
I have all of those plus the Crossover plugin and they all work fine, even in Galeon. The Java plugin for Mozilla is different than the one for NS 4.x. You may want to check to see what your system is using for the MOZILLA_FIVE_HOME environment variable. If you installed it using the rpms, that is set to /usr/lib/mozilla and the location for system wide plugins is going to be /usr/lib/mozilla/plugins. If you want to put them someplace else, I _think_ you can as long as you set LD_LIBRARY_PATH to include the directories where you actually installed the plugins.
the good ground has been paved over by suicidal maniacs
Erm, wouldn't that mean that 1.0 should have been hit on the 5th iteration?
What version of OS was Microsoft pushing when Mozilla got started anyway? I'm thinking it was Windows 98 first edition. In the mean time they've had 3 major upgrades to that, the last of which was a total overhaul.
Sorry, just something that occurred to me as I was reading this. As Mozilla has been working on this browser, it's primary environment has been a moving target. One of the downsides of how long this is taken I'd imagine.
The line must be drawn here. This far. No further.
note: i'm predominantly running windows lately on my desktop machine. don't start with me. it's the curse of being a gamer.
.02
last year i ran in to NetCaptor (http://www.netcaptor.com), which, uses IE and, among other things, is "tab-able", and i simply can not go back now. (i'm addicted to tab-able apps. PowerShell rules! having 20+ windows open at any given time doesn't). so, my suggestion to developers is an add-on app that incorporates Moz for this. i'm sure i'm not the only one that would love to see this.
just my
alive to the universe, dead to the world
yes. now all you need is a way to call [aspell or ispell] from the browser and somehow usefully use its output...
Pspell is a portable C library providing an interface between apps such as Mozilla and several varieties of spell-check backends (such as Aspell's English algorithm or Ispell's language-independent algorithm), along with command-line apps that call those functions. It's licensed under GNU Lesser GPL.
Oh, and aspell/ispell is Unix-only,no?
No. Pspell is a cross-platform library, and even though Ispell is tuned for POSIX systems, Cygwin provides a good POSIX layer on Win32 systems. With the port of XFree86 4.10 to run on Windows 98/ME and Windows NT/2K, it's very hard to call a piece of source code "designed only for UNIX systems" anymore.
Will I retire or break 10K?
It just makes life harder on web designers. How can we optimize our HTML code to render correctly in your browser, if you lie to us about what browser you're using?
If your browser sends
then the server will send IE content, but the web designer will notice the satanic "666" in the User-Agent field of the logs and know something is up. A closer inspection reveals a Mozilla browser.Will I retire or break 10K?
Yes, and don't forget ctrl-Q, which will instantly close all windows ( in case of emergenecy ;-) ).
Flash plugin opens
So, here's a list of what you can really do:
yush
I'm not certain (check the newsgroup post) but I think it disables them during timer events as well.
Gerv
It's turned on by default (in installer builds only) because we would like more people to test it. You have an option of turning it off in the installer.
Yes, we are trying to make the code more efficient as well - turbo is not a substitute for performance improvements.
Oh, and the mozillaquest.com article is full of it.
Gerv
So what's Netscape 6.1 (released early August, to widespread acclaim) if not a product?
Gerv
There's a sourceball on ftp.mozilla.org and you don't need the website unless you want weird build options. The command you are looking for is:
:-)
gmake -f client.mk build
Hope that helps
Gerv
There are a whole slew of bugs in textarea handling that make it very difficult and painful to compose posts in textareas. This is not so critical for people who don't, uh, participate in large discussion groups such as this one. But if you DO post to Slashdot etc., you may want to hold off -- until 1.0, which is the target for just too many of these bugs, IMO.
/. their bugzilla, but I'm talking specifically about such bugs as 83650, 82151, 88024, 68331, 75629, and 74383. And, for example, as I compose this in Moz, I know that if I accidentally hit the right arrow button at the end of the post, the cursor will move to the top of the post. It's painful.
I won't link in the bugs since the Moz folks don't like us to
Does anyone know where I can find out how to set up Mozilla to use mutt as its mailto: handler? Google couldn't tell me anything useful.
It's your codebase too should you decide to jump in and write some code. If you have performance insightss that you think warrant action please post them to Mozilla's performance newsgroup
--Asa
Just so that everyone knows - it appears that the CVS variant of Galeon works fine with Mozilla 0.9.4.
What doesn't render correctly? As of now, IE4/5/6, NS6, Mozilla 0.9.3+ and derived browsers and Opera5 all render HTML4/CSS1/etc. per the standards. Some include proprietary extensions, but all of them handle standards-compliant HTML4 correctly. NS4 doesn't but then NS4 doesn't do HTML4/CSS1, having been designed and built before those standards were finalized. Now if you mean they render the HTML differently, that's true, but then they're allowed by the standard to render it differently. The basic idea is that the browser should render things the way they ought to be rendered on the client system, which can vary from system to system as look-and-feel differs.
Of course, you might be trying to do precise page layout and such. Don't. You don't know anything about the client system, so trying to do pixel-level control of layout or force page widths and such doesn't work. I hate pages that make me scroll horizontally because they were designed for a wider screen than I've got, and I hate pages that leave half my browser window blank because they were designed for an 800x600 screen and my system's 1600x1200 on a 21" monitor.
As for frames, I've seen more than a few pages that, when hit with Mozilla 0.9.3, tell me I need a frames-compatible browser. They do this because they've got a hard-coded list of browsers that support frames, and anything that isn't on that list is assumed not to whether it does or not. Worse yet is the site that requires frames but only uses them for a navigation/menu sidebar. Oddly, if I take that side, scan the source and put in the URL to the nav/menu frame manually, I can navigate the site just fine. I've got to hit the Back button to get the menu back to change areas, but it's entirely navigable and usable without frames even though it was designed to require it. And all it takes is one anchor tag in the NOFRAMES section, but the designer won't do it.
There was an article here on /. and people were talking about popup windows, and I said that it would be nice to be able to disable window.open on a per site basis. I wonder how they implemented this. If it was a global thing for all sites or per site. But this is cook.
Only 'flamers' flame!
actually, if it were exponentially, it would be the zeroth generation.
And I suspect he meant monotonically asymptotic, but that is a bit of a mouthful.
</pendant mode>
What it *does* do is allow you to specify sites or pathnames from the root of any site that simply don't load. If it's an image, you get a broken image thingie. If it's a page, junkbuster tells you that the page is blocked.
It can also acti in a similar manner with cookies.
But it never, ever, changes things, and has no universal settings. They explicitly refuse to offer those (though they do tell you how to find sites where you can see what others have done).
hawk