Post by Mike M on Jan 10, 2015 4:29:30 GMT 1
thanks for your nice Add-On.
I would suggest you place some kind of Howto on whitelisting ATR in Noscript, as it is blocked on every website. I haven't figured out how to circumvent this, without having to completely disable Noscript.
Post by Admin on Jan 10, 2015 20:28:33 GMT 1
Thanks for report, Mike.
I've considered the problem but unfortunately there's no facility in Firefox's API to allow for a solution be developed by my side of the binomial ATR/NoScript incompatibility.
As per specification, prosed here
, web scripts
and content scripts
are two set of scripts designed to be insulated from each other. Web scripts
are those scripts provided by a website when a page is downloaded, while content scripts
are those provided by installed add-ons.
As NoScript appears to be blocking content scripts
too, it is crossing the intended insulation border, authoritatively preventing other add-ons from executing their own content scripts
. This insulation is only suggested by the specification but is not enforced by Firefox, so add-ons are allowed to interact — or interfere — with each other.
It is possible that other add-ons remain functional with NoScript active, because NoScript is not allowed to block main scripts
and worker scripts
other add-ons may suffice for their functionality; only content scripts
may be blocked, on which ATR depends upon, and NoScript appears to be blocking them. The problem should be discussed with Giorgio Maone, developer of NoScript.EDIT:
as a workaround, since ATR 1.8 right clicking on selected text provides a context menu with an option to synthesize the selection. This should still work even if the content script is blocked.