Mozilla 1.4 RC3 Is Out
zzxc writes "Mozillazine reports that the third release candidate for Mozilla 1.4 has been released. It is available for download from mozilla.org. Testing is encouraged to fix any bugs before the final release. No new features have been added to this release, though many bugs have been fixed. For more information, see the release notes."
Mozilla 1.4 RC3 is expected to be the final release candidate. It incorporates the fix for one final GDI leak bug, and some minor stuff, but unless something completely unexpected will crop up, this very same release candidate will be rebranded as 1.4 final by the end of the week.
Firebird a subproject of Mozilla is a light weight version of Mozilla seems a lot better bet to me.
:)
Actually, the current Mozilla Roadmap clearly states this goal: Deliver a Mozilla 1.4 milestone that can replace the 1.0 branch as the stable development path, then move on to make riskier changes during 1.5 and 1.6. The major changes after 1.4 involve switching to Mozilla Firebird and Thunderbird, and working aggressively on the next two items.
So actually, that's where we're heading
.: Max Romantschuk
When Moz 1.4 final is released, will Firebird then be based on 1.4, or will it remain based on the Moz 1.3 codebase? Also Moz needs better default fonts still. I had to install the vera fonts to make it look decent. In IE the fonts looks so much better. I know, thats becasue its using the fonts in windows and what not, and moz just can't include anti aliased fonts that won't work on systems x,y and z, but there needs to a system with prebuilt decent fonts. Moz is now so much better than IE, but default Moz on linux looks like a POS. Yes yes I installed truetype fonts now its fine but a lot of people don't know how to do all that. All this is becasue I had installed linux for a non computer person, who updated mozilla and then was stuck with the default fonts.
I had long noticed this also. You used to be able to go into their ftp directory and hunt down the RH7.x version.
/usr/lib. Then copy your plugin modules and links to modules (read the latter: j2re) into the new mozilla directory. You might have to modify a couple of the permissions on the mozilla or its subdirectories, and maybe put a link in /usr/local/bin. If you are a little careful, it is not bad at all.
/usr/lib
Actually, it's nearly trivial to install their tar.gz packages. It involves unpacking in
> cd
> ls -ld moz*
lrwxrwxrwx 1 root root 14 May 31 06:20 mozilla -> mozilla-1.4rc1
drwxr-xr-x 5 root root 4096 May 31 06:18 mozilla-1.3
drwxr-xr-x 10 root root 4096 May 31 06:24 mozilla-1.4rc1
To-do List: Receive telemarketing call during a tornado warning. Check.
8 of 13 people found this answer helpful. Did you?
Then what about Thunderbird?
in mozilla, type something in the adress bar , press down key and you get "search google for" , press enter and boom results are there.
I don't want to switch to a different search field or even set up parameterized keywords to do this.. Google search with 2 keys (down + enter) is for me the killer feature as i do this well over a hundred times per day
No, just scroll down. After the release notes, there's a section "New additions to the Release Notes".
Here's the documented "changes". Very subtle.
Mozilla 1.4 RC 2- Mozilla 1.4 for Linux requires Sun J2SE v 1.4.2 Beta to run Java applets
- JavaScript access to Flash does not work on Linux Mozilla 1.4
Mozilla 1.4 RC 3Speak truth to power.
That's just a clarification of the stuff about Java, it's not indicative of a change between releases.
...
As you might expect, the only changes between RC2 and RC3 were a bunch of bug fixes, and those don't get mentioned in the release notes - they're release notes, not a changelog.
For the sake of the database, I won't post bugzilla links, but the list of fixes since RC2 is as follows:
88393 (Mac) Check in a high-resolution application and document icon
140357 (All) Backspace deletes text formatting,TypeInState should be s...
189429 (All) strict javascript warning in mail3PaneWindowCommands.js
197379 (Mac) file:// URLs from CFM mozilla don't work with Mach-O mozilla
199443 (PC) leaking GDIs when table cell contains an image, and text...
205360 (Sun) libxpcom.so depends on non-existent libiconv.so
206271 (PC) News Messages being marked as read automatically
206668 (Mac) [Mac OS X classic theme] context menu only work on frontm...
208560 (PC) P3P summary only works once
209033 (Mac) FIXE (Shockwave, Flash, ?) all typed letters (from kbd) appear...
209354 (All) typeaheadfind causes major memory leaks
Now for the heart of my complaint. In Mozilla 1.2 and before, once you had focus on the location bar, double-clicking the location bar selected all, just as it does in Internet Explorer and numerous other Windows apps that have boxes for file names and URLs.
In Mozilla 1.3, the behavior was changed to: double-click selects a "word", and triple click selects all. The philosophy being, the location bar is like a mini text editor, so it should work like an editor. See this Usenet thread. (Frankly, the "word" that is selected after double-clicking has never been of much use to me.)
The problem is, I think (this is my theory) there is something fundamental in Windows where "triple-click" is not a real operating system event, like double-clicking, so some other kludge is used to time the clicks. Or maybe Windows XP or the mouse driver is just broken, I don't know. But anyway if I have the mouse speed set for fast clicking, I can't get triple-click to work at all. If I set the mouse speed slow, I can triple-click as long as I click not too slow and not too fast, but you have to get the timing just right. Half the time it seems I get it wrong and have to try again. And I hate having to set the mouse speed slow because that screws up what I'm used to with other apps.
I know this isn't the right forum for bug reports - I've been meaning to study this problem in more detail, logging Windows events and times so I can make a convincing case and write up a useful bug report, but time has just been slipping by and I'm afraid the final release (an important one from what I hear) will happen before this can be properly addressed. I will try though, I promise. :)
Am I just being fanatically nitpicky, or does this bother anyone else? (Well, at least I got it off my chest...:)