not working in Firefox Nightly (FF57) about javascript-toggle-on-and-off

[robinwhittleton]

Working for me in today’s Nightly. Tested on https://google.com/maps which gives you a blank page with no JS available.

[0c1]

The result is approximately as before. It did appear to work a little but mostly not. The config value javascript.enabled is not changed by toggling the add-on.
My user agent is : Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
I'm running Nightly: 20170904100131 (the update of 9/4)
The javascript toggle add-on was re-installed this morning to insure it's at the latest level

[rNeomy]

It works fine for me too. Note that the extension has a test page. Right-click on the toolbar button to open the test page.

If you have an example site that the add-on is not operating as expected please provide the link.

about:config javascript.enabled (true|false)

WebExtension add-ons cannot change internal preferences. The extension uses WebRequest API to block JS execution.

[0c1]

It is working to the extent that it can in FF57. It does block javascript execution. It does not override the configuration setting javascript.enabled in about:config. If javascript.enabled is set false, the add-on has no effect. It cannot cause javascript to run if javascript.enabled is set false.

If the javascript.enabled is set true then the add-on can block javascript.

Perhaps the description or FAQs could be modified to include this detail?

[0c1]

After trying it more, Google search results with javascript.enabled set FALSE is not the same as relying on the add-on to effectively disable javascript. With real javascript disabled (javascript.enabled FALSE) the result of a google search looks different from [javascript.enabled TRUE and the add-on in place, togged to off].

[rNeomy]

Google search results with javascript.enabled set FALSE is not the same as relying on the add-on to effectively disable javascript.

When the extension is enabled, Google does not know it and hence tries to load the page as JS engine is enabled. But when this flag is set to FALSE, Google knows that browser has no JS engine and hence loads no JS version of itself.

As far as I know, the extension can block all the JS executions just fine.

[0c1]

Long term, the result of using this extension is that it would appear to content providers that almost all Firefox users have javascript enabled. Currently, web developers have to consider a larger minority of readers do not allow javascript.

On a further point I'm not in a position to test, many of those fake email messages that say 'FedEx couldn't deliver your package' or 'your Amazon order was cancelled' try to get people to access their bad website with javascript enabled. Has this add-on been tested against such a rogue, especially if the rogue thinks it just connected to someone with javascript enabled?