Slashdot Mirror
Mozilla 1.2 Unleashed
asa writes "Mozilla 1.2 has just been released. New to this version are features like Type Ahead Find, basic toolbar customization (text/icons/both), support for GTK themes on Linux, multiple tabs as startpage,
Link Prefetching, "filter after the fact" and filter logging in Mail, Palm sync for Mozilla addressbook on MS Windows, and more. This is the latest stable release from mozilla.org, and all users of Mozilla 1.0, Mozilla 1.0.1, Mozilla 1.1 or any of the alpha/beta/release candidates are encouraged to upgrade to this release. You can get builds and more info at the Mozilla releases page and you can find daily Mozilla news and discussion at mozillaZine.org."
So not all things are available unless you use the classic theme-that sux.
This SIG pulled due to lack of funding. (This damn war is costing too much!)
Actually, as Phoenix is a cut-down version of Mozilla, it means we shall soon "type ahead" with it too.
BTW, Mozilla is better for those who also want an integrated mailer, we're not discussing the very same app, here...
Trolling using another account since 2005.
less than 7% of my million monthly hits are something other than Internet Explorer
it's a damn shame esp. when Mozilla is now the superior product.
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
What happened to it? The last time this worked was around 0.95 or so. Having to restart to change themes is, for one thing, primitive, and another, a pain in the butt.
Anybody know what's going on here?
Life's a bitch but somebody's gotta do it.
Sure. You want a web browser these days, you use Phoenix. You want a "communications suite" that lets you chat, send email, etc, you get Mozilla. Different goals.
Of course, since you change a single #define and then compile Moz to get Phoenix, I'm not sure that you can really say that you aren't using Mozilla...
May we never see th
This was posted using Mozilla 1.2
Sex - Find It
Last I heard, Red Hat only ran on x86. Or actually I remember they had an S/390 distro too.
On other x86 distributions, you at least have the hope of using alien to switch the package format. But I use Debian on a PowerPC Macintosh.
I'm pretty sure Macromedia wrote software for the Macintosh before they even had any products for Windows. Flash right now is supported on the Macintosh, so the software is supported on PowerPC architecture.
How about getting us a Flash for Debian PowerPC Linux?
The "Red Hat" only mentality is why I think there isn't much hope of companies succeeding in shipping proprietary products for Linux. People on other distros or architectures get particularly irritated that they can't do whatever the product provides and write an open source replacement, where they wouldn't have bothered if the commercial app supported all the platforms.
If a bunch of volunteers working for no pay can support, what is it? 8000 packages on eleven architectures, why can't a commercial vendor support all the major Linux distros and architectures?
Request your free CD of my piano music.
One of the last uses I had for explorer was to browse CNN. Mozilla 1.1 had problems formatting HTML on some (most) CNN articles;
Upgraded, tested, and now it works like a charm. What is that procedure to remove IE again?
I can't believe they still haven't incorporated "single window mode" into the built-in tabbed browsing features of Mozilla. Every person I've talked into trying Mozilla wants to know why windows still open all over the place when they're using tabbed-browsing mode. Instructing them to go find an obscure plug-in, and then configure it, is not an acceptable solution for Joe Mousepad.
P.S. The default theme is impossibly ugly. ORBIT
// I will show you fear in a handful of jellybeans.
Trusting the site owners is not the same as trusting the content from its users. I trust the slashdot people, I don't trust the trolls that are posting goatse links.
True warriors use the Klingon Google
I would prefer to see more articles describing how to avoid proprietary IE methodologies, like document.all in favor of w3c standards. In most cases there is a standard-compliant way of doing things. If IE has some worthwhile proprietary features maybe we should be encouraging w3c to adopt them, but it is a slippery slope to conform to IE-only features.
-- Solaris Central - http://w
Remember that Mozilla is two things, a browser and a development platform.
You bring up an interesting point. If I may nitpick, I've always held that "Mozilla" is two things: a development platform first and a internet communications suite second.
You say "browser," I say "internet communications suite." What's the difference? Well, the former renders web pages but the latter lets you do that and then some. Calling Mozilla (the software) just a browser is like calling Microsoft Office a word processor or calling a PalmPilot an electronic addressbook. When I mean to talk about the portion of Mozilla that renders web pages, I try to refer to it as Mozilla Navigator. Likewise for Mozilla Mail & News, Mozilla Composer, Mozilla Addressbook, and Chatzilla. Referring to these components by names can clear up a lot of confusion that some people have, especially those who aren't familiar with the whole Mozilla project.
Not that I'm going to *insist* that people correct their naming conventions, it's just that my method makes more sense to me.
Now if only they'd fix the download manager in OS X (it shows nothing right now, and hasn't for quite some time), and add an option to automatically close the download manager if all downloads have completed successfully.
I'm extremely wary about the new prefetching feature in Mozilla. The Web caching community has tried this from about every angle, but the general consensus of professionals (with one notable exception) is that prefetching is a bad approach.
For one thing, it assumes free bandwidth; not such a hot idea in a lot of places (e.g., Australia, where you pay per Mb).
I've also had network and server administrators calling me in a panic because they're being flooded with requests from a single machine - whoops.
Prefetching is generally pretty antisocial; it says "my browsing experience is so important, damn your network, damn your servers, I'm getting it all!"
This doesn't mean that it isn't of great interest to the research community, of course; go to any caching-related conference and you'll see earnest proposals for prefetching (along with yet more hyper-optimised replacement algorithms... *sigh*).
Specifically, I'm concerned that the Mozilla implementation won't fare any better; in one way, it's better that it uses explicit prefetching hints (rather than some "optimized" algortithm... I hate heuristics), but OTOH it's horrible; this is ripe for abuse by over-zealous webmasters. I wonder how long it'll be before we see a demo of a DOS attack based on this...
Also, not providing a preference UI to control this isn't so bright; Mozilla has matured past the "world is my debugger" stage, at least in this respect. There are legitimate reasons for turning this off; in fact, I think there's a strong argument for turning this off by default.
Phoenix isn't SUPPOSED to do that! Phoenix is just a browser. Mozilla is a suite of internet applications that includes HTML authoring. Phoenix is just the browsing components of Mozilla stripped out and refined to provide a smaller, faster, simpler interface.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
SlashDot uses them -- look at the document nav bar in Moz/Opera, you'll see Next/Previous, which go to the next/previous story. Unless you have a habit of reading every article, Moz will pointlessly prefetch the next story up, and you'll happily ignore it. Users who used to (e.g.) read every other story now actually end up fetching every story anyway.
:P
rel="prefetch" is fine, rel="next" makes me nervous. I don't want content providers to stop using rel="next" because of the deranged behavior of some clients
If slashdot uses link rel=next and no one uses it then why are they including it in the source? Authors use this tool to specifically connect pages. It is assumed that people will be navigating to the next document linked or the author wouldn't include that tag. Authors who are using link rel= next that don't want people navigating to that linked document shouldn't be using next so you shouldn't be nervous about content providers stopping use of the tag. What have you lost if slashdot removes the tag if, as you suggested, no users actually uses the link rel=next to get to the next article?
--Asa
(Yes, I've tried posting to the Mozilla newsgroups, but this is exactly the kind of request that gets ignored by everyone there.)