Firefox 2.0.0.8 Versus IE7 - IE WINS!

Sweet mother of all that is holy! How could IE7 possibly top Firefox 2.0.0.8 on any kind of objective playing field?!? Granted, I was a little doubtful at first as well. Sure, the newly downloaded experience of either is somewhat similar, but Firefox has hundreds of professional grade extensions/add-ons to customize your browser experience, right? WRONG!

A bug in 2.0.0.8 that isn’t yet officially recognized by Mozilla completely fubars ALL extensions. A plea for help on the forums results in the tired “delete extensions.blah blah blah from your profile and everything will be fine.” Nope! Previous extension get stuck requiring a restart, or just dissapear, or falsely claim to be incompatible. Reinstalling them doesn’t help. I’ve even got one extension that’s been claiming it will be uninstalled after the next restart. It’s been saying that for the last dozen or so restarts.

Moral of the story? This has nothing to do IE, I just wanted a scandalous title. Oh, and avoid the 2.0.0.8 update like an axe-wielding vampiric pedophile with bad personal hygiene in a dark alley on a full solar eclipse in the middle of a continent-wide blackout.

Tags: , , , , , , , ,

This entry was posted on Saturday, October 20th, 2007 at 6:20 pm and is filed under Commentary. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Firefox 2.0.0.8 Versus IE7 - IE WINS!”

Drew Loika October 21st, 2007 at 9:02 pm

sigh

FACT: I know how to use Google and I found the Mozilla help on fixing broke extensions
FACT: I used that info and exited Firefox and deleted the three extensions.* files.
FACT: staged-xpis didn’t exist
FACT: I still had almost as many problems as I had extensions
FACT: Just for giggles I decided to do it again today, and this time there WAS a staged-xpi’s folder
FACT: My disappeared extensions have returned and all are working?!?

Sweet. Gotta love it when software makes you look like an idiot. Believe me or not I tried that fix before I ever posted on the Mozilla forums in the first place, but for whatever reason it worked today. So cross me off the list of outstanding issues, but I stand by my claim that something screwy was introduced with 2.0.0.8.

Regardless, thanks to the forum members who replied for all the suggestions, and thanks to Mozilla for the (newly reinstated) #1 browser on the market.

Leave a Reply