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.
Yeah.. take a look at the CSS standards at W3C, and see how good it is.
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.
No IE favorites import. :( It's broken again. Back to Bugzilla....
Skip Franklin
It's always darkest just before it goes pitch black. -- despair.com
Well I can't square what you say with what I see. The production release of 1.3 is snappy. At least as fast as 1.2.1.
Maw! Fire up the karma burner!
How about this ?
Guvf vf abg n EBG zrffntr
F3 or Ctrl-G
What a fool believes, he sees, no wise man has the power to reason away.
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...
Hasn't about:config been there for a while?
Yes, it has. But with 1.3, it's now editable. Now you can load it up and make direct changes to the prefs right in the browser window.
--Asa
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.
It'll work when bug 104174 is fixed.
Guvf vf abg n EBG zrffntr
Strangly enough, thats not way I would Build Mozilla. Usualy I use these to get what I want, this includes all sorts of goodys, that are not just font specific. Also I shy away for the "-march=i686" but I do use O2.
ac_add_options --enable-crypto
ac_add_options --enable-ldap-experimental
ac_add_options --enable-optimize=-O2
ac_add_options --enable-reorder
ac_add_options --enable-cpp-rtti
ac_add_options --enable-cpp-exceptions
ac_add_options --enable-default-toolkit=gtk2
ac_add_options --disable-toolkit-gtk
ac_add_options --enable-xft
ac_add_options --enable-freetype2
ac_add_options --enable-oji
ac_add_options --disable-debug
ac_add_options --disable-short-wchar
ac_add_options --with-system-zlib
ac_add_options --with-system-jpeg
ac_add_options --with-system-png
ac_add_options --with-system-mng
ac_add_options --disable-tests
"think of it as evolution in action"
If you want the old one, get it from bug 93093.
And save it as "mozilla.bmp" in your Mozilla folder.
Guvf vf abg n EBG zrffntr
> 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.
IE has the ability to insert arbitrary HTML which makes table insertion much easier. We had to use DOM manipulation for our demo. I haven't added IE specific code for table insertion yet.
As far as the API goes, we worked very hard to make the API compatible with IE.
If you want to understand how we differ from IE, see:
http://www.mozilla.org/editor/ie2midas.html
I have on my todo list to make the demo work better in IE. In particular, I'd love to get the button look and feel working better in IE.
If you're running OS X on that PowerBook, then no, this won't affect you. The bug affects OS 9 and lower.
They usually appear a while after the actual release.
Look on ftp.mozilla.org for the previous Mozilla releases, they have md5 checksums.
Guvf vf abg n EBG zrffntr
It's important to those of us that have to use multiple browsers for one reason or another. There are lots of cases where a site is only viewable in IE (or vice versa, although that's much less common). This is especially bad if your company develops Int(er|ra)net applications, as mine does.
.URL file formats haven't changed recently - certainly they're simple enough. But somehow this feature keeps breaking. It's a reason for me not to use Mozilla, and if Mozilla is ever going to become a general user phenomenon, it needs to be working flawlessly. Joe user won't switch unless we make it extremely easy for him to do so.
The "who cares" mentality seems to exist at the Mozilla developer level as well, since this bug keeps popping up again and again. I'm almost positive that
The obvious next comment is "get the source, fix it yourself, submit a patch". If I get the time, maybe I will, despite my less-than-stellar C++ skills.
Skip Franklin
It's always darkest just before it goes pitch black. -- despair.com
The slowdown in pace is even part of the Phoenix development plan, if any bothered to look.
Together, we will drive the rats from the tundra.
if your like me and you don't use the download manager but have dialogs enabled, you will eventually find that downloads will continually take longer and longer to start. Eventually I ended up with a 10 second lag between clicking save, and the application actually saving. Turns out Mozilla logs all downloads in the download manager anyway and NEVER purges the list. You can improve performance by deleting the file 'downloads.rdf' in your profile directory (this of course nukes your download history).
Just in case anyone else has been having a problem with huge delays in downloads starting.
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=16296Am I the only person who noticed that they cravenly removed the Mozilla mascot from the splash screen?
This will sound stupid to the Slashdot Crowd, but many of the people that I've switched to Mozilla really, really liked the mascott. I've even had several of the women comment that they used Mozilla because they thought the logo was cute; the guys though it looked cool (these people are not technical types).
Why they would switch to the current bland and antiseptic splash screen is beyond me. I mean, I'm not going to switch browsers or anything, but they do risk alienating at least a fraction of their "joe six-pack" user base. Plus it's just dumb from a marketing standpoint.
Bring back the fire-breathing lizard!!!!
If you agree with me, vote for the bug I submitted to Bugzilla.
Help save the critically endangered Blue Iguana
It screws Windows up to due to the nice intergration. It only seems to use less RAM because of it's nice intergration. Also you can compile/configure Mozilla to use considerably less RAM if you're really worried about it.
:)
You can use Mozilla with your native widgets if you really want to. Having widgets shared between platforms is excellent if you move between multiple OS's and want them all to be familiar. Also Mozilla allows you to modify the look of the browser using CSS which lets you do some really useful things.
Frequent patches are a feature not a bug. You don't have to wait months for a security fix you should have in days. Not everyone makes as horrible patches as Microsoft that break as much as they fix. Nobody forces you to download the patches when they are offered.
Opera is sort of ugly but not as ugly as IE.. well except for the free version that has that ass ugly ad banner in the toolbar. I've never had it crash on me but I only use it for testing.
IE goes down more than a crack ho. It locks up for no reason whatsoever on certain sites. Sure the sites are probably horribly coded but it shouldn't freeze up. It's not much better than Nutscrape 4.x.
Of course the best web browser of all time is Lynx. It does what you need and nothing else. Pictures are for wimps and commies.
At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
It's only a minor annoyance, but Mozilla doesn't yet snap to the default button in Windows if that setting is configured in Control Panel (when set, the mouse cursor should automatically move to the default button in dialog boxes). You might think it wouldn't be such a tough fix, but it's apparently ellusive :-/.
If you like, you can vote for the bug (you'll need a free Bugzilla account to vote). You'll probably need to copy-n-paste the URL, as Bugzilla doesn't accept referers from Slashdot.
Alex Bischoff
HTML/CSS coder for hire
or this bookmarklet:
Guvf vf abg n EBG zrffntr
I am still using 1.3b and went to the listings link you had (http://www.tvguide.com/listings/), put in my zip code, chose cable, chose the appropriate provider and got a list of shows.
When I click on any of the shows, a window pops up and has the description in it, just fine.
Perhaps it is from constantly upgrading and not a fresh install? ie, legacy properties?
I have recently upgraded my machine and have only 2 versions besides 1.3b (1.2b and 1.3a) that I have upgraded from and perhaps that is the cause for the discreptancy.
... one is the quick launch "feature'O'bug".
this problem is much deeper than it appears to be. It's directly connected to the memory leaks issues. whether bad mozilla code or bad C libs implementations are guily for these is still debated on bugzilla. I guess there is no hope to see this baby fixed until a mjor new version emerges (2.0?).
in my opinion this is the biggest problem this cool browser has and it's getting pretty old.
... second is the ATI drivers doodoo.
i don't know just how big this one is but the fact that a browser admits to have problems with all of the latest ATI drivers is totally unacceptable.
i would propose them to extend this problem over nvidia cards so that we all go for matrox.
"Where's my home button?"
Oh, right here.
It's the first thing I do when I re-install Moz.
Get Firefox!
The DNS cache is supposed to be flushable by going offline, then online again. Currently, it's broken, however. Eventually, it will be fixed. http://bugzilla.mozilla.org/show_bug.cgi?id=192798
If you're running a nightly build, and you're expecting it to be stable, well, that's your own fault, isn't it?
Go to http://bugzilla.mozilla.org/.
If the latest nightly is crashing consistently and repeatedly, try to search for an existing bug report, and if you can't find one, submit your own. Somebody else who's more familiar with Bugzilla will probably find the existing bug you couldn't find, and mark yours as a duplicate, so at least make the effort to search before submitting, but don't feel too bad about it. If it's really not a duplicate, somebody will try to reproduce it, and if they can, it will get fixed. If they can't, it'll be marked "works for me" and closed, so make sure you leave detailed steps on how to reproduce the bug. You'll be notified by e-mail as people add comments or change the status of the bug (and if it gets marked as a dupe you'll be notified of updates to that one too). When it's marked as resolved, wait a day or so and then try the next nightly.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
...when you're downloading in the middle of a slashdotting, and it's *still* going at max speed. Sigh.
Either that, or perhaps AOL/Time Warner has a hell of a lot of bandwidth at their disposal? Hmmmm... largest ISP in the world, huge media conglomerate, lot of bandwidth...
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
Actually, I've been awaiting it's arrival for quite some time.
h scroll
Perhaps it's just IE's implementation of smoothscroll that annoys you.
I haven't seen what the smooth scrolling for Mozilla will look like, but it shouldn't be too far away. I would hope that the Mozilla guys have thought it out a little better than the IE team. We shall see.
http://bugzilla.mozilla.org/show_bug.cgi?id=smoot
With the above, right click and copy-paste it into another browser window. Also, note that the bug has an alias "smoothscroll" so you don't have to remember it's number.
Withdrawal before climax is very ineffective and those who try this are usually called "parents."
Does anyone know how to change the order of the right click tab menu for
the windows version? Before it had "new tab" on the top, now "close tab" is
the top one.
You get to the menu by right-clicking anywhere on the tabs bar.
I really hate Dan Patrick.
We have XBL to let us seperate concerns. Check it out.
Fortunately, you can return the functionality by putting the following line in your prefs.js file:
If you think using C++ is the cause of their slowdown you are extremely misinformed.
I agree, the 95% figure is way off, but he has a point. And most of the sites you are talking about (or at least the ones I've seen that resemble what you are talking about) are just old. It's not due to poor design, though. It's because they were made in an "era" when there was the IE way to do it or the Netscape 4.7 way to do it (layers) and neither way was standard but it was the only way to do it. Now Mozilla and Netscape 7 come along and don't support (or fix the support) of the Netscape 4.7 DHTML/CSS model and thus, the sites don't look right. But since IE still supports a lot of its older, IE-only stuff, the sites still look OK. I don't know if I agree that Mozilla should support "IE's DHTML model," but the problems aren't caused by poor site design, because the sites weren't poorly designed at the time.
There are obvious exceptions to this so please don't give me a big list.
I'm just saying, it's not an accident the sites worked in any browser. It's most likely that they worked in only one at the time because it was the only way to do it. Or the only feasible way to do it; who is going to write 38 lines of this-browser-only code when "this.hide" works in what 98% of the traffic is using? Probably not many people.
This may be an unpopular view, but this effort reminds me of the way another desktop environment developed. Creating more and more apps that rely on the mozilla codebase makes it central to the desktop... rather like IE.
To my knowledge, no desktops require Mozilla to work. Sure, GNOME has Nautilus (still? Or did they shitcan it?) which has Mozilla embedded, and Galeon is the GNOME browser, which has Mozilla embedded. However, and this is important. If Mozilla goes a direction these guys don't like, they can fork the code or put in a new renderer. YOU are not stuck with Mozilla, and you can change your directory browser (as far as I know, in KDE you can) and your default browser, and so forth.
The idea of making the browser integral with the desktop isn't inherently a bad idea, it's just that Microsoft did it specifically to drive Netscape out of business. Also, in doing so, Microsoft opened up holes in their system so big that Windows is now a whore to script kiddies. Any embedded MOzilla application doesn't run the risk at this time. (it might one day, but I don't think so)
It might be an unpopular view as far as Mozilla is concerned, just try to keep in mind that when you're talking about Free Software, the situation changes. It doesn't make it right (although in this case I think it is right), but it does change the way you have to evaluate the situation.
Like what I said? You might like my music
Opera shrinks or magnifies images along with text, just press 0 to step up, 9 to shrink and 6 to reset to 100%. Also, 8 adds an extra 100% while 7 takes it away. There's also a handy dropdown list to change it for each window.
Opera 7.03 was released the same day as Moz 1.3. Go get it!
Use ISO 8601 dates [YYYY-MM-DD]