Firefox 7.0 released

broni ...

First, let me say that I have not made the suggested change in about.config.

To test your statement, I copied the URL from this page and pasted it into a TB composition window and the http:// was included. I sent the message to myself and, after receiving it, I clicked on the link and it opened this webpage.

I also tried it several other times with other websites, and every time the http:// appeared and the webpage opened.

It also works if the link is attached to a word (or words) in a TB message.

Why my FF 7.0 installation should behave differently from others, I don't know but, apparently, it does.

 

I wasn't trying to be "right ", but I couldn't (and don't) understand why this supposed bug doesn't happen for me while, apparently, it does for others.

 

Firefox 7.0.1 was released today thursday 29 sep 2011 to correct the disappearing addons problem.

 

Here's some more confusion for you. I've just had the latest FF Beta 8 installed.
The usual Addons will be compatible at a later date. All running smoothly at the moment. Neil.

 

Addons trail FF release by at least 3-4 weeks. So by the time most of the addons become compatible, its time for a new FF release & the cycle repeats itself. Whew.

I think they are changing something about addons in FF 8. Another round of broken & non working addons.

 

If you can't wait for your favorite Add-on extension (yes, they're still called extensions) to be updated, here's something you can try. Usually, it will work.

If you don't keep a folder of your favorite extensions, download those that don't work from Firefox Add-ons.

Right-click on the "Add to Firefox" button and select "Save Link As... ".

Rename the downloaded file, such as example.xpi, to example.zip.

Unzip example.zip.

Open the install.rdf file in any text editor.

Look under <!-- Firefox --> for em:maxVersion>n.n</em:maxVersion>.

Change n.n to a number higher than the version number of FF that you're using (I'm using FF 7.0.1 right now, but have set the max version number in my extensions to 10.0) and save the changed file.

Rezip all of the unzipped files and folders, giving the new zipped file a name that better reflects the purpose of the extension, such as (for the purpose of this little tutorial) newexample.zip.

Rename newexample.zip to newexample.xpi.

Install newexample.xpi using FF's Add-ons Manager.
​

Your updated extension probably will work. If not, it needs to be re-worked by its author.

 

Have not had a problem with an add-on for a long time using
Add-on Compatibility Reporter :: Add-ons for Firefox

 

Flatiron2 ...

I used the same extension for a long time, as well, but it didn't seem to make any difference, as all it does (if you let it) is report an incompatible extension to the Mozilla team.

FWIW, Add-ons include themes and plug-ins. What we're talking about is extensions. Am I the only one who gets that? (Sorry for the rant ).

 

Likewise! Some people who are detesting the rapid release of FF and TB are ridiculing the developers for the release of this update. I have, never, had a problem with my extensions with FF7.0.