Comments on: Changing the checkCompatibility preference http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference Spouting nonsense from the depths of my spare time Tue, 02 Mar 2010 15:42:15 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Alex M. http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-42441 Alex M. Thu, 25 Feb 2010 05:54:54 +0000 http://www.oxymoronical.com/?p=671#comment-42441 Hi, so what happened to the ability to see which extensions are working under force-installed mode? Does anyone else regret not being able to see that anymore? There used to be a red exclamation mark next to all the extensions which are technically incompatible (even after I overrode compatibility with NTT). This time, after I enabled NTT and did "override all compatibility", it disappeared. :( Hi, so what happened to the ability to see which extensions are working under force-installed mode? Does anyone else regret not being able to see that anymore? There used to be a red exclamation mark next to all the extensions which are technically incompatible (even after I overrode compatibility with NTT). This time, after I enabled NTT and did “override all compatibility”, it disappeared. :(

]]> By: Firefox 3.6 now available for download - Mozilla Links http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-40094 Firefox 3.6 now available for download - Mozilla Links Thu, 21 Jan 2010 18:33:55 +0000 http://www.oxymoronical.com/?p=671#comment-40094 [...] For future versions you will need to set extensions.checkCompatibility.3.7 to false and so on. See Dave Townsend’s post for more [...] [...] For future versions you will need to set extensions.checkCompatibility.3.7 to false and so on. See Dave Townsend’s post for more [...]

]]> By: Zsolt http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-39102 Zsolt Fri, 08 Jan 2010 11:16:57 +0000 http://www.oxymoronical.com/?p=671#comment-39102 And now they will be recommending the new way. The change was only successful in creating frustration for everyone. And now they will be recommending the new way. The change was only successful in creating frustration for everyone.

]]> By: Mossop http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-36503 Mossop Tue, 01 Dec 2009 16:29:14 +0000 http://www.oxymoronical.com/?p=671#comment-36503 Leaving the old setting working would have clearly not had the effect that we intended with this change, people would have gone on recommending that to users and we would still be in the same position that we were. See also http://blog.mozilla.com/addons/2009/11/13/burning-down-the-add-on-review-queues/ for updated information on AMO reducing the review queues. Apparently I was slightly mistaken above when I said the average was a week, that is true for updates, new nominations are done in around 2 weeks. It's also worth remembering that votes on a bug report are just a small measure of how many of a certain class of people want to see something fixed, something that is related to but not the same as how important a bug is to fix. It is difficult to truly measure the latter. Leaving the old setting working would have clearly not had the effect that we intended with this change, people would have gone on recommending that to users and we would still be in the same position that we were.

See also http://blog.mozilla.com/addons/2009/11/13/burning-down-the-add-on-review-queues/ for updated information on AMO reducing the review queues. Apparently I was slightly mistaken above when I said the average was a week, that is true for updates, new nominations are done in around 2 weeks.

It’s also worth remembering that votes on a bug report are just a small measure of how many of a certain class of people want to see something fixed, something that is related to but not the same as how important a bug is to fix. It is difficult to truly measure the latter.

]]> By: patheticcockroach http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-36467 patheticcockroach Tue, 01 Dec 2009 09:27:02 +0000 http://www.oxymoronical.com/?p=671#comment-36467 Simply the most retarded update in Firefox's history (until the IU revamp of version 3.7 or 4 gets released). Why didn't you just let the old generic "extension.checkcompatibility" setting and added your awful new "extension.checkcompatibility.[version here]" as an extra setting? I guess you thought maybe my pref.js is too short and needs one line per Firefox version (also counting alphas and betas)... Not to mention the fact that it took me a week to find out why my Classic Compact theme wouldn't load anymore... This bug 521905 wasn't a bug, but "fixing" it introduced one hell of a regression. Not to mention the fact that it had only 4 votes while a real and annoying bug like Bug 83376 (Crash loading Java Plugin if UserAgent string is changed), reported in 2001 and with 36 votes still isn't fixed. Trying to push me more towards Opera or Chrome? Don't push too hard, you could succeed sooner than expected... On a side note: +1 to Michael Buckley for the terrible extension approval delay and the random rejection reasons (a way to spare t-shirts at the cost of screwing a few thousands of users?) Simply the most retarded update in Firefox’s history (until the IU revamp of version 3.7 or 4 gets released). Why didn’t you just let the old generic “extension.checkcompatibility” setting and added your awful new “extension.checkcompatibility.[version here]” as an extra setting? I guess you thought maybe my pref.js is too short and needs one line per Firefox version (also counting alphas and betas)…
Not to mention the fact that it took me a week to find out why my Classic Compact theme wouldn’t load anymore… This bug 521905 wasn’t a bug, but “fixing” it introduced one hell of a regression. Not to mention the fact that it had only 4 votes while a real and annoying bug like Bug 83376 (Crash loading Java Plugin if UserAgent string is changed), reported in 2001 and with 36 votes still isn’t fixed. Trying to push me more towards Opera or Chrome? Don’t push too hard, you could succeed sooner than expected…

On a side note: +1 to Michael Buckley for the terrible extension approval delay and the random rejection reasons (a way to spare t-shirts at the cost of screwing a few thousands of users?)

]]> By: Oliver http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-36075 Oliver Thu, 26 Nov 2009 12:22:20 +0000 http://www.oxymoronical.com/?p=671#comment-36075 same here on b4, it doesnt have any effect same here on b4, it doesnt have any effect

]]> By: Zsolt http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-35600 Zsolt Thu, 19 Nov 2009 19:42:49 +0000 http://www.oxymoronical.com/?p=671#comment-35600 It worked for me. Just added "extensions.checkCompatibility.3.6b" and set it to false It worked for me. Just added “extensions.checkCompatibility.3.6b” and set it to false

]]> By: Krayon http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-35596 Krayon Thu, 19 Nov 2009 18:23:07 +0000 http://www.oxymoronical.com/?p=671#comment-35596 Really not liking this extensions.checkCompatibility change. I tried adding a new boolean with 3.6 and it didn't work. Nor did NTT. Back on 3.6b1 until you sort this mess out. I'm on OS X. I copy/pasted the boolean from this page (and removed the full stop) to double check. There's no chance I did it wrong. It just didn't work. Really not liking this extensions.checkCompatibility change.
I tried adding a new boolean with 3.6 and it didn’t work. Nor did NTT.
Back on 3.6b1 until you sort this mess out.

I’m on OS X.
I copy/pasted the boolean from this page (and removed the full stop) to double check. There’s no chance I did it wrong. It just didn’t work.

]]> By: Jeff http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-35595 Jeff Thu, 19 Nov 2009 18:09:58 +0000 http://www.oxymoronical.com/?p=671#comment-35595 My apologies. It looked to me like this change was the reason why FF 3.6B3 now does not allow me to Override Compatibility on individual AddOns using NTT. My apologies. It looked to me like this change was the reason why FF 3.6B3 now does not allow me to Override Compatibility on individual AddOns using NTT.

]]> By: Zsolt http://www.oxymoronical.com/blog/2009/11/Changing-the-checkCompatibility-preference#comment-35585 Zsolt Thu, 19 Nov 2009 14:36:31 +0000 http://www.oxymoronical.com/?p=671#comment-35585 How annoying. Now I'll have to disable compatibility checking every version number change... YAY! So what if people start to learn this method too? You'll just gonna generate a random property name with every version? Don't you guys have better things to do than screwing up functionality that works perfectly? How annoying. Now I’ll have to disable compatibility checking every version number change… YAY!
So what if people start to learn this method too? You’ll just gonna generate a random property name with every version? Don’t you guys have better things to do than screwing up functionality that works perfectly?

]]>