hackademix
script being blocked for a split second, impossible to allow it
it is impossible to allow a script that is part of a sequence, such as the payment gateway on btmobile website. I woul have thought there would be a history option at this point so we can go back and retroactively allow scripts for a domain, noscript has been going for ages, right?
I agree, this makes it really annoying to find out what is wrong with websites where this happens. Have to go in the browser's dev console to figure out what is being blocked by noscript, and then go to the noscript preferences to add the url manually to allow it.
It would be great if all blocked URLs for a page just showed up in the main interface. Maybe those part of a sequence could be colored differently to be able to identify them?
It would be great if all blocked URLs for a page just showed up
I know this wasn't your exact meaning, but the use of that particular word triggered an idea... In fact, if you could hit a "More" button in the NoScript dropdown and bring up a dialog which listed every domain and all of the exact script URLs so far blocked/allowed, grouped by domain... That would be fantastically powerful, and need not clutter up the default user experience at all. This way you can not only sort out the above issue (because you would list every script attempting to load from every domain in the current instance), but give power-users even more granular control at their fingertips. Okay, perhaps allowing sub-subdomain control would necessitate another display setting in the normal dropdown ("Custom" or such), since you don't want to show "Untrusted" or "Trusted" when it's halfway in between - but it still seems like an idea very much worth pursuing. 🤓️
I clicked on this topic because I've also had the issue of a script being blocked and then the page does some sort of internal mini-reload and the script is no longer listed to allow... And at least a couple of times this has happened like a redirect; I think that could make it harder to implement the above, since you're having to then consider scripts from the 'last' page and not just the current one, which WOULD be a real mess, and impractical for the add-on. Hmm...
Didn't there used to be a "block refresh/meta refresh" and/or "block redirects in <noscript> tags" option in NoScript? This would be a very useful feature in this scenario. 🤔️
