NoScript 10 Needs UI for Viewing/Editing xssUserChoices

[barbaz]

Please add a UI for viewing/editing/deleting the individual xssUserChoices in NoScript 10 Options. The lack of such UI makes it overly hard for users to investigate and fix problems such as viewtopic.php?f=8&t=25254 .

Thanks

(I seem to recall this was requested before, but search isn't turning up any such thread.)

[therube]

How does an XSS setting even get... oh, you're going to tell me it's from one of those popup dialogs that you get.
And in that dialog there must be a checkbox, to remember or something or the other.
Oh.
And so now you're saying that once a person has checked that box, there is no (straight forward) way to know that they had, much less to affect a change.

+1

[barbaz]

Bump.

We've just had at least two more threads about this -
viewtopic.php?f=8&t=26162
viewtopic.php?f=7&t=26161

[Sirus]

+ 1

I found out we could edit the XSS list by exporting the NoScript config (Export > noscript_data.txt > search for "xssUserChoices" and modify) which would be a workaround in the meantime while we wait for someone to code a proper UI, but that doesn't work; importing a modified noscript_data.txt doesn't stick - when I export the config afterwards, it's always the same old config. Even if I restart the browser in between.

Any thoughts? Should I flag this as an import bug?
Thanks!

[Giorgio Maone]

Importing a modified noscript_data.txt doesn't stick - when I export the config afterwards, it's always the same old config. Even if I restart the browser in between.

The most likely reason for such a behavior would be your edits causing the JSON to become invalid.
Could you double check? (I'm adding a more explicit failure mode for that in 11.1.7, BTW).
Also, in order to clear the XSS settings you need an empty xssUserChoices property (

Code: Select all

xssUserChoices: {}

).
Just removing it outright would not work: is that your case?

[Sirus]

Correct! Indeed, I left a comma ( , ) when I removed the last entry, effectively making the JSON invalid. Having a proper error message would've made me find the issue.

And also correct, flushing all my saved XSS choices is what I wanted to avoid.

Looking forward to that new version with explicit failure!
Thank you!!