SillyDog701

[Anonymosity]

I just got Firefox 13, and it immediately marked 4 of my themes as incompatible. All these had the max version in the install.rdf file bumped up to version 20.*, yet Firefox would not accept them until I reinstalled them. It is quite happy with them now. This is in spite of the fact that the oldest theme I have was apparently quite acceptable. What makes Firefox decide that an add-on is incompatible now? It is evidently not just the max version setting any more.

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20100101 Firefox/13.0

[Antony]

So you are saying that Firefox bumps itself to Firefox 13, and your themes became incompatible? (Until you re-install the themes.) Nice! I guess that's the joy of chasing to the latest version or even worse, pushing users to the latest version.

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20100101 Firefox/12.0 AlexaToolbar/alxf-2.15

[Anonymosity]

No, Firefox did not update itself (I disabled that). I downloaded version 13 and installed it. I do not understand why it should decide that some themes are incompatible arbitrarily while it finds others acceptable. With the oldest theme I have (not updated since Firefox 5), it was perfectly happy.

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20100101 Firefox/13.0

[Fulvio]

I had a similar situation with one addon , i.e. Quick Restart. Quick Restart is marked as incompatible in both FF13, and the separately installed FF13 beta. FF13 which was formerly 12, does not have a string :extention.checkCompatibility13.0, user set, boolean, false, which would allowed it to work, but, rather a default, which does not seem to work. I have no idea how to change the strings, or delete them in about:config.
I have had no problem, getting addons to work, till this new v.13.

UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0

[Anonymosity]

"FF13 beta. FF13 which was formerly 12, does not have a string :extention.checkCompatibility13.0, user set, boolean, false,"
That setting is there. You misspelled the word extension. It is EXTENSION.

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20100101 Firefox/13.0.1

[Fulvio]

Code: Select all

You misspelled the word extension. It is EXTENSION.

Going to my post, I can see that I spelled as "extention". It was an error, even pointed out by the spell checker. I do hurry at times, so I misspell. But, my misspelling does have anything to do with the issue in question.

UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120715 Firefox/14.0.1 SeaMonkey/2.11

[Anonymosity]

extensions.checkCompatibility.13.0
I have that setting in about:config. I copied it from there. I do not see why it would not be present in Windows as well as in Mac OS.

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0.1

[Fulvio]

We got sidetracked in my misspelling, but, I had never implied that the line is missing in my PC. However, check compatibility does not mean, to me: make compatible. I interpret check compatibility, simply, what it says. If it is not compatible, you will know.i
The trick is to make incompatible extensions, compatible. That's where the Add-on compatibility Reporter add-on became very useful.

UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1