Slashdot Mirror

It's appears to be a common practice. The Linux kernel contains many swear words, and so does Mozilla.

I can't remember seeing one lately.

Bug 217527 (that screenshot is a pretty severe case). Look it up in Bugzilla for more screenshots and discussion (Bugzilla links from /. don't work so I won't bother with linking to it). I'm not sure, but it may be worse in Windows, I don't recall whether it happens in Linux since I usually use Mozilla Suite when I'm in Linux.

The bug is definitely still present in 1.0 final since the devs decided to keep the fix out of the 1.0 branch, which is what prompted me to package up the extension.

Perhaps a third of computers seem to not be affected at all by this problem, at least judging from my small sample set (I have one friend who uses FF 1.0PR and browses Slashdot and says it doesn't happen at all for him). For me, it happens on both my desktops and my laptop, so I'm 3 for 3 on my computers, and it happens on at least 75% of /. pageviews.

Even when the slashdot bug has already been filed for Firefox, it won't be available until Firefox 1.1 (aw crap).

In other news, Slashdot would REALLY do Firefox users a favor if they implemented things like this (Main page here, article here).

I mean, isn't this what web developers have been saying for AGES? "It's NOT the browser, but the WEB DESIGNER'S FAULT!".

So, can somebody explain to me WHY /. won't fix their webpages to a CSS layout? I mean, look at what can be done with CSS! Look ma, no layout!

https://bugzilla.mozilla.org/show_bug.cgi?id=21752 7

Not linked, because bugzilla disallows slashdot as a referrer. If you read the comments, they had a fix, but the fix broke a bunch of other sites. This blog post sums things up pretty well too.

Read the details at bugzilla.m.o bug 195280. It was around June 3 I think. Several people have linked to an XPI that you can install to restore MNG support to post-June-3 builds. Try http://stud4.tuwien.ac.at/~e0225227/.

There is a much older bug to restore MNG support but if you feel the urge to comment in bugzilla be sure to read the rules and add something useful...

Most of this info is summarized in this Blogzilla entry

Christopher

Favicons (site icons) have been disabled in the Personal Toolbar and the Bookmarks menu for a while, due to caching issues. They're still in Phoenix, and possible some of the third-party extensions at mozdev.
A search of the n.p.mozilla newsgroups turned up this guide to restoring them. I haven't tried it, though, so I have no idea if it works, or what it may screw up.
For details of the caching issues - see bug 120466

Bloated? Subjective. Uncheck the components that you don't want to install.

Slow? Semi-Subjective. I don't know what type of CPU you have but it runs acceptably on a PII400 with 128 MB of RAM at my job.

Full of senseless features? Subjective and not even worth keystrokes to refute.

IE 6 and Mozilla 1.0 CSS2 Errors here

Opera 7 CSS2 Errors here

Looks like Mozilla still has the least buggy CSS support (going by number of flaws). Also note that NO browser fully supports CSS2.

I know that Mozilla at least partially supports CSS3 selectors. Here's a way to block ads using them.

Also, look no further than MSXML version 1 (pretty much useless now) for the problems with supporting drafts. Thankfully it's easily replaced.

We all have our reasons for using our web browsers but the only thing that I see Opera 7 having a clear advantage in (on the systems that I routinely use) is startup time. Everything else is negligible to me. But maybe that's just me.

You can do this with a cookperm.txt file.

Ad Blocking with Mozilla has some good info. You can also use this in Chimera to some extent. For more info Google it.

go moz...

Mozilla/NS6.2+ also has this: Keywords for your bookmarks, including keywords that take a parameter. I use 'g whatever i'm looking for on google' and 'ng whatever i'm looking for on google groups' or 'imdb star wars' etc etc all the time.

I found a great write up of it here.