InformAction Forums

So. Clean install of Firefox Stable, fresh install of NoScript as of today 2018-08-21. 10.0.0.100 mydev in my hosts file.

If I access http://mydev:8080/something Noscript immediately blocks it (good)

However, if I click on "trusted", nothing happens.
This appears to be a bug in the NoScript widget, since going to the full noscript configuration page and manually adding http://mydev:8080 works, at which point the toggles in the display work correctly.
This bug seems to happen any time I access a site without a domain.

Also, a separate question that ma1 might not be able to do anything about. If I'm on a site, and I accidentally or on purpose touch the Reader icon on my toolbar (happens by accident pretty easily on Firefox Mobile), it appears that noscript is immediately cut out of any of its site restrictions - for example playing embedded videos. I was wondering if that was in fact that case, if ma1 had filed a bug w/ mozilla on this (or did not consider it a bug) and if so, just how much of the site actually runs in reader mode (workers? videos? all javascript? plugins?)

nemo wrote:So. Clean install of Firefox Stable, fresh install of NoScript as of today 2018-08-21. 10.0.0.100 mydev in my hosts file.

If I access http://mydev:8080/something Noscript immediately blocks it (good)

However, if I click on "trusted", nothing happens.

Does this problem persist with latest development build?

nemo wrote: If I'm on a site, and I accidentally or on purpose touch the Reader icon on my toolbar (happens by accident pretty easily on Firefox Mobile), it appears that noscript is immediately cut out of any of its site restrictions - for example playing embedded videos. I was wondering if that was in fact that case, if ma1 had filed a bug w/ mozilla on this (or did not consider it a bug) and if so, just how much of the site actually runs in reader mode (workers? videos? all javascript? plugins?)

It's unlikely NoScript (or any other extension) can interact with reader-mode page in the near future, at least looking at the discussion in this bug.
The page gets apparently sanitized, but if that's a concern I could try to check whether the current tabs.toggleReaderMode() API allows me to prevent NoScript-restricted pages from being accidentally opened in reader mode.