InformAction Forums

Hi I need help!
I'm virtually computer illiterate so having searched all the FAQs and read sites on the new NoScript i am none the wiser.
My problem is I do not understand how to use the new NoScript with the new Firefox57.
I always used to (on the old version) just temporarily allow the page but now I'm presented with a list which I do not understand, so I don't know what I'm supposed to allow or not.
At the moment I can;t even make a simple online purchase as something is obviously not allowed on the site I'm on and I don't know what to do I've even tried temporarily allowing the whole page but that doesn't seem to work.
I also (on almost every site I go on- which are every day sites like Matalan or Southeastern Trains) get a big blue box coming up saying there's a XSS and even if I click Allow it just keeps coming up and preventing me from using the sites.
Sorry this is long and rambling but I'm at the point of thinking I'm going to have to remove NoScript because I just can't use my computer.
Any help would be gratefully received but as I say I don't understand computer jargon.
Thanks
Teresa

https://forums.informaction.com/viewtop ... =7&t=23974

is a good writeup to understanding the new ui

Thank you I will read it and hopefully it may help. Can you just tell me what is ui?

guest wrote:Can you just tell me what is ui?

User Interface

Hello Teresa,

Like you, I was completely stumped by the new interface. The write-up suggested by Pansa is very thorough. For those of us who just want to temporarily allow only the sites necessary to get the content we want, the process is actually quite simple. Skip down to the "Temporarily allow scripts for a domain" section for the answer. Basically, click on the blue "S" (after the word "Default"), this will temporarily allow the site.

It's really odd that core functionality like this is now difficult to figure out. A lot of people are having a hard time with this (check the reviews... yikes!). It should be like it was before, words that say "temporarily allow"... or at the very least, when you hover over the trusted icon it should say "temporarily allow", not "trusted". It's somewhat misleading. Good app design requires special attention to the UI; if this extension isn't easily understood by novice users adoption will be low.

Hope this helps,

Charles

Hi Charles
Thank you for your reply, yes it's very difficult for a real novice like me as I really don't know what I'm doing but I will have a good read of the explanation!
I'm really hoping it will explain how to stop the big blue XSS boxes appearing constantly too.
thanks again and I'm sure I'll be back with questions soon.
Teresa

HI there, I've read the helpful explanation of NoScript, thank you to blublevita for that and also thanks to Charles I have worked out how to temporarily allow pages. However I'm still having issues as I'm still not sure what I should actually be allowing (temporarily or not). Sometimes I go onto a page and a long list of things comes up on the NoScript and I'm just not computer savvy enough to know what each one is and if I should allow it or not! I wish NoScript would go back to the way it was previously.
Also I am still plagued constantly with the Big blue XSS boxes that keep popping up also asking if I want to allow, sometimes allow or block things! I DON'T KNOW if it needs to be blocked or allowed. Very frustrated and hoping that amendments can be made to make it more user friendly for people like me.
Sorry for the rant
Teresa

guest wrote:I'm still not sure what I should actually be allowing (temporarily or not). Sometimes I go onto a page and a long list of things comes up on the NoScript and I'm just not computer savvy enough to know what each one is and if I should allow it or not!

It's just trial-and-error. Best you can do is reduce the amount of trial-and-error. Here's one way - https://forums.informaction.com/viewtop ... 314#p75314

guest wrote:Also I am still plagued constantly with the Big blue XSS boxes that keep popping up also asking if I want to allow, sometimes allow or block things! I DON'T KNOW if it needs to be blocked or allowed.

Even I can't always tell. My suggestion with XSS warnings is, if you don't know what to do, block it and ask on this forum. Be sure to include full details of what NoScript flagged as potential XSS.

Thank you barbaz, it is indeed trial and error which is frustrating.
I don't think I could ask on the forum about the XSS blue boxes as I seem to get 2 or 3 come up every time I go online and I think people would be sick and tired of me asking but thanks again for your advice.
Teresa

guest wrote:Thank you barbaz, it is indeed trial and error which is frustrating.
I don't think I could ask on the forum about the XSS blue boxes as I seem to get 2 or 3 come up every time I go online and I think people would be sick and tired of me asking but thanks again for your advice.
Teresa

Well, what you are doing with this addon just isn't specifically intuitive, nor is it "intended" by the people coding the pages in the first place.
It's not really a fault of noscript.

You are basically cherrypicking which part of a website you want to execute or not. And since the page code isn't supposed to be "where end users go at all", it is hidden behind cryptic and rarely easy to read domain names.
But that was the case with the old no script as well.

As for the xss calls, I rarely get them, but that'S because have my default set to "nothing allowed", which means the calls aren't even loaded to begin with (in most cases), unless I temp allow a domain that tries to XSS to begin with.
That. too, is something to blame webdesigners for, rather than noscript.
It used to be understood that XSS calls are not proper coding, and only maliciously used, but somehow in the last couple of years standards have declined and now every half baked web designer thinks they can get away with not coding a proper [script]section.