Slashdot Mirror
Mozilla.org Launches Mozilla 1.3
theBrownfury writes "Mozilla 1.3 is out and about. New to this version are features like image auto sizing, bayesian junk-mail filtering, dynamic profile switching, about:config for a pretty view into all of Mozilla's "secret" settings, an initial version of Midas for rich text editing, and a lot of other fixes for performance, standards compliance and site compatability. Also with 1.3 Mozilla is now applying machine learning to improve the autocomplete feature. Mozilla 1.3 is now the official stable release from mozilla.org. Users of all previous versions should upgrade to 1.3 for the latest in features and stability. More info at the 1.3 release page and discussions at mozillaZine.org."
If you haven't been using the 1.3 preview releases, and so haven't been running the spam filters yet, remember they take a while to get going. Look at http://www.paulgraham.com/spam.html , the results are for around 8000 sorted messages. Just keep correcting it and you'll be fine.
I'm scared of numbers that can't be written as a fraction. It's an irrational fear.
...you can now use a version of Galeon later than 1.2.7 without worrying about a dodgy beta copy of Mozilla. In the past if I'd wanted 1.2.8 I'd have to download and use the possibly unstable Mozilla 1.3 beta.
Get Mozilla 1.3 here and here.
Note to M1-ers: a curt but otherwise insightful message is not "Flamebait" or "Troll".
The Konqueror web browser that comes with KDE 3.1 plays both MP3 and Ogg Vorbis!
Religion is the main cause of atheism.
Everything you need to know, step by step, can be found here.... I've been building AA/TrueType support into Mozilla for a while now, and I have no idea why it's not enabled by default, or why others don't config their builds to do the same. Mozilla looks like absolute shit without smooth fonts.
Additionally, you can find a webcam movie of me eating a donut by clicking the link below.
Bowie J. Poag
Autocomplete doesn't use machine learning in 1.3. It was an experimental, disabled-by-default, feature in 1.3beta for data-collection.
If you read the ML autocomplete page, the main "feature" in 1.3 is logging what entry people tend to pick from the autocomplete list; this will be fed into development of the ML autocomplete. They have a super-alpha version of the engine in there, sure, but really what you should be doing with 1.3 is feeding them the info. Don't expect intelligent autocompletion.
Unfortunately they still haven't added NTLM support. If you're in a total Microsoft shop with a MS proxy, if the admin has it totally secured, nothing other than IE can be used. Having this feature in Mozilla will help reestablish it as a corporate browser....and help some of us who can only use IE.
Oh and the bug is 3 years old. I know some work is being done on the Windows Mozilla, but damn. Three years?
m.kelley
life is like a freeway, if you don't look you could miss it.
The RPMs for RedHat 8 have the Xft support enabled. (They're not released yet, but they probably will be soon.)
It's not enabled by default because it requires libraries (Xft2, fontconfig) that many users don't have. At some point someone might modify the code so that it tests for the presence of the library and loads all the required function pointers manually, but that's a bit of work. What's available now is good enough for distributors and good enough for people who know to get the RH8 RPMs.
It's bug 176715 and should be fixed by Mozilla 1.4: http://bugzilla.mozilla.org/show_bug.cgi?id=176715
What a fool believes, he sees, no wise man has the power to reason away.
How about this ?
Guvf vf abg n EBG zrffntr
Automatic image resizing is off by default in Mozilla (although on by default in Phoenix), and can be toggled by clicking on the image.
I have to say I don't like it much either. For Phoenix users, it can be turned off by adding user_pref("browser.enable_automatic_image_resizing ", false); to user.js in the profile directory, or by manipulating the browser.enable_automatic_image_resizing preference in about:config .
I'm sure the Mozilla gods have blessed us with a config option to disable this "feature."
Actually, you have a preference to _enable_ the feature. It's off by default. Also, once enabled (by going to Edit->Preferences...->Appearance and checking the box titled "Enable automatic image resizing") a simple click on the image will restore it to its original size.
This really is a friendly implementation. I much prefer it to the feature implemented by the other guys.
--Asa
It was moved to "Popup Windows" under the "Privacy & Security" tab in the Preferences.
You are aware that mozilla is hosted in AOL's datacenter, arn't you? Good luck slashdotting it.
From domainwhitepages.com:
OrgName: Netscape Communications Corp.
OrgID: NSCP
Address: 501 E. Middlefield
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
NetRange: 207.200.64.0 - 207.200.127.255
CIDR: 207.200.64.0/18
NetName: NETSCAPE-CIDR
NetHandle: NET-207-200-64-0-1
Parent: NET-207-0-0-0-0
NetType: Direct Allocation
NameServer: NS.NETSCAPE.COM
NameServer: NS2.NETSCAPE.COM
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 1996-09-06
Updated: 2001-03-28
TechHandle: AOL-NOC-ARIN
TechName: America Online, Inc.
TechPhone: +1-703-265-4670
TechEmail: domains@aol.net
I think AOL can hold up aginst a slashdotting...
The nightly builds support AA but it isn't enabled by default. I'm using this in my user.js:
pref("font.FreeType2.enable", true);
pref("font.FreeType2.autohinted", false);
pref("font.FreeType2.unhinted", false);
pref("font.antialias.min", 0);
Looks good to me!
Check out the Progress and Future of Mozilla-the-application-suite for information on what's coming up in the next few months.
> Maybe it's a Mozilla bug and not an ATI bug?
If you look at ATI's release notes for their newest drivers, they explicitly list this as an ATI bug.
> why is Mozilla the only application affected by
> this bug
Because Mozilla happens to tbe the only app you have that uses the particular functionality that's buggy in the driver, whatever that is? How many apps do you use that do transparency, translucency (fast, mind you), background tiling in hardware, etc?
That the idea to use it as a platform to develope portable applications (using ECMAScript + XUL) is catching on slower than some people would expect. This is a pity, because ungodly amounts of effort goes in making this possible, and still people see it just as a web browser (a large one).
Other than that, Mozilla-the-web-browser is fine, Mozilla-the-messaging suite is at least good enough, and Mozilla-the-javascript-debugger shows lots of promises.
I don't include Mozilla-the-IDE (Komodo) in the list, since it deviates too much from the usual distribution (even if it is Gecko Inside(TM)).
Now waiting for Mozilla-the-organizer (thru Calendar, planned for 1.4 ~ 1.5). Perhaps a Mozilla-the-file-manager would be something worth implementing (but Meow seems definitively dead).
"Tools | Mark Selected Messages as *Not* Junk"
There have been a bunch of posts to the newsgroup and this has been the problem.
Unless you tell the filter what is spam *AND NOT* spam then it only has half of the information it needs to make a decision. It's a bimodal decision tree that is used to determine whether a message is spam or not. ie;
for each word {
the probability it is spam is x
and the probability it is ham is y
}
A calculation (Bayes) of those probabilities intersecting usually places the probability that any given message is spam either close to 1 (spam) or 0 (ham). What happens if you don't train ham is the probability of all messages will be around .5 and that is not enough to say anything definitively and defaults to delivery.
Who are you? The new #2 Who is #1? You are #617565. I am not a number, I am a free man! Muhahaha.
1.4 nightly builds have support for profile chrome. That means that extension developers can make extensions that install to your profile and won't get erased when you upgrade your Mozilla binary.
--Asa
Until recently add-ons could only be installed in the Mozilla application directory, where they get deleted every time you upgrade to a newer version.
A bug was recently fixed that makes it possible to install add-ons into the user profile directory, where they persist through upgrades.
Note that until 1.4alpha comes out, this fix will only be available on the nightly builds. Also, add-on authors have to modify their add-ons to install into the profile directory. If you are an add-on author, see the bug for an example of how to do this:
http://bugzilla.mozilla.org/show_bug.cgi?id=16296