[WARNING] Nightly might break some add-ons

Posted November 21st, 2015, 12:37 pm

Be forewarned. I discovered an add-on breaker on inbound. See my bug report if this is why your add-on broke. As of this post it hasn't made it to Nightly.

1226869 – Bug 1182546 Breaks some add-ons

Some resources are now blocked by Bug 1182546 and require a contentaccessible=yes to be added to affected add-ons chrome.manifest.

This only applies to Fx45. The other builds will eventually get the offending patch through the normal propagation of builds.

***** UPDATE *****

Bug 1182546 is now on Nightly.

Posted November 21st, 2015, 3:12 pm

I am going to make this into a sticky and create a sticky in the extension dev forum pointing to it.

Kindly report such stuff in this thread.

Posted November 21st, 2015, 3:15 pm

Another issue reported before:
let and const compliancy breaks some add-ons.
viewtopic.php?f=23&t=2966543

Posted November 21st, 2015, 3:53 pm

Quicksaver add-ons are broken by this patch. I contacted him and he has updated all his add-ons. At this point in time they are not available. You can always add the line to the add-ons manifest.chrome yourself. Here's all his add-ons: User Info for Quicksaver

Posted November 21st, 2015, 3:55 pm

Easy fix for downthemall. If you extract and open chrome.manifest with Word just add contentaccessible=yes to the second line so it reads like this:

content dta chrome/content/ contentaccessible=yes

Posted November 21st, 2015, 3:55 pm

It's been reported that AdBlock Plus is also affected by this patch. You can add the line to ABP's manifest.chrome if ABP hasn't been updated yet.

Posted November 22nd, 2015, 6:37 am

Won't opening and editing an extension also break the required / soon to be required signature of the extension?

Posted November 22nd, 2015, 5:34 pm

Thanks for reporting this streetwolf. A few add-ons of mine are affected too.

Posted November 22nd, 2015, 7:00 pm

The Tinsmith wrote:Won't opening and editing an extension also break the required / soon to be required signature of the extension?

Not in Nightly. Requirement will only stand in Beta and Release. Nightly and Aurora/Dev don't have the requirement so they can be used for testing extensions without modifications.

Posted November 22nd, 2015, 7:28 pm

patrickjdempsey wrote:
The Tinsmith wrote:Won't opening and editing an extension also break the required / soon to be required signature of the extension?

Not in Nightly. Requirement will only stand in Beta and Release. Nightly and Aurora/Dev don't have the requirement so they can be used for testing extensions without modifications.

I see. That does sound sensible.

Thanks for the information.

Posted November 24th, 2015, 9:11 am

Aris wrote:Thanks for reporting this streetwolf. A few add-ons of mine are affected too.

Are CTR and/or CTB among them?

Posted November 24th, 2015, 9:47 am

CTB yes, CTR no.

Posted November 24th, 2015, 9:52 am

Aris wrote:CTB yes, CTR no.

Thanks, Aris.

Posted November 25th, 2015, 3:05 am

Tab Counter isn't working either. How do I add this to the manifest?

Posted November 25th, 2015, 4:17 am

Grantius wrote:Tab Counter isn't working either. How do I add this to the manifest?

Open that add-ons chrome.manifest file and edit this line:

Code: Select all: content tabcounter-morac chrome/content/

in this:

Code: Select all: content tabcounter-morac chrome/content/ contentaccessible=yes

Make sure to delete the META-INF folder and to disable add-on signing or you won't be able to install modified add-ons.

[WARNING] Nightly might break some add-ons

Who is online