You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that installing RP for the first time on Fx 4.0b7+ results in a non-working RP. There's an error about the use of __LOCATION__. Probably related, Fx now keeps the xpi as an archive on disk, not extracted. This may explain why an existing RP install continues working after upgrading Fx: the xpi is extracted and __LOCATION__ works.
The full error:
{{{
Error: LOCATION is not defined
Source File: jar:file:///path/to/.mozilla/firefox/asfdsafd.profilename/extensions/requestpolicy@requestpolicy.com.xpi!/components/requestpolicyService.js
Line: 432
}}}
The text was updated successfully, but these errors were encountered:
Fixed in r361. I have a feeling the reason I didn't use this solution before was probably because I wasn't adding the correct resource line to chrome.manifest when I had tried. I probably was using a jar: reference even though the modules directory isn't in requestpolicy.jar (which only includes content/, locale/ and skin/).
It appears that installing RP for the first time on Fx 4.0b7+ results in a non-working RP. There's an error about the use of
__LOCATION__
. Probably related, Fx now keeps the xpi as an archive on disk, not extracted. This may explain why an existing RP install continues working after upgrading Fx: the xpi is extracted and__LOCATION__
works.The full error:
{{{
Error: LOCATION is not defined
Source File: jar:file:///path/to/.mozilla/firefox/asfdsafd.profilename/extensions/requestpolicy@requestpolicy.com.xpi!/components/requestpolicyService.js
Line: 432
}}}
The text was updated successfully, but these errors were encountered: