Closed Bug 1387807 Opened 7 years ago Closed 7 years ago

WebExt, uBlock Origin/uMatrix and others need a clean way to disable javascript and change other security/privacy setttings.

Categories

(WebExtensions :: Untriaged, defect)

55 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1367161

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 Build ID: 20170616223046 Steps to reproduce: 1. Disable scripts by default in either uBlock Origin or uMatrix. 2. Go to a site which contains a <noscript> tag. Actual results: Because uBlock Origin and uMatrix use CSP to block JavaScript execution, the noscript tag is not activated and the site is broken. Expected results: The website should believe that javascript is disabled and should display the noscript tag's contents.
Additionally, this can (theoretically) be solved in legacy extensions by setting user preferences (http://www-archive.mozilla.org/projects/security/components/ConfigPolicy.html), but this will not be possible in WebExtensions.
Component: Untriaged → Add-ons
Product: Firefox → Tech Evangelism
Version: 55 Branch → Firefox 55
I don't think this is an add-ons issue. If websites show <noscript> content when JS is disabled via CSP, then presumably the same should happen for add-ons, and it should be fixed in Firefox. If they don't, then I don't think there's anything to fix and the bug should be closed.
Component: Add-ons → Untriaged
Product: Tech Evangelism → Firefox
Version: Firefox 55 → 55 Branch
> If they don't <noscript> tags do not render if javascript is forbidden a CSP set by by the site itself. Anyways, given that a CSP can forbid selectively only some specific sources of javascript, it's really not obvious what the solution would be if the issue was considered valid.
Assigning a component and perhaps there's someone with extensive knowledge on this area that might be able to help here.
Blocks: CSP
Component: Untriaged → DOM: Security
Product: Firefox → Core
This would not be correct behavior for CSP. I appreciate the cleverness exhibited by these extensions to approximate the effect they want, but it's a horrible hacky way to do this and we should instead give security-focused extensions a set of security knobs they can fiddle. Disabling javascript is only one of the many things lost when access to general preferences was taken away. Bouncing over to webextensions as a request for a security API.
Component: DOM: Security → WebExtensions: Untriaged
Product: Core → Toolkit
Summary: WebExt, uBlock Origin/uMatrix → WebExt, uBlock Origin/uMatrix and others need a clean way to disable javascript and change other security/privacy setttings.
We already have a bug for disabling javascript on individual sites. The bug summary refers to "other security/privacy settings". We have some existing browser.privacy apis, if more are needed please open new bugs and be specific about what is needed.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.