Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with the <noscript> tag #2845

Closed
chiraag-nataraj opened this issue Aug 6, 2017 · 1 comment
Closed

Dealing with the <noscript> tag #2845

chiraag-nataraj opened this issue Aug 6, 2017 · 1 comment

Comments

@chiraag-nataraj
Copy link

I know there have been other issues dedicated to this (e.g. #308). After doing a little research, I found that there was a remedy for this, but that that remedy will be inaccessible after the webext transition. Before, you could use browser preferences to set it up so that javascript was actually disabled on certain sites (see here). However, the new webext API won't provide access to browser preferences, which means this won't be fixable - at least not in this manner (as far as I can tell, that's how NoScript used to handle it).

@chiraag-nataraj
Copy link
Author

chiraag-nataraj commented Aug 6, 2017

Submitted a Buzilla bug here. Let's see what happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant