|
Not really. If you can figure it out, you can play with the XSS exceptions. I don't understand it, the syntax of the exceptions list, well enough myself to explain it.
XSS refers to cross-site scripting, which NoScript blocks by default.
There's really no good reason for a website to use this, but some rather big ones have started to do so. It's used in some billing situations, where it really can be dangerous, and academic libraries or similar sites that act as a portal to other content. As an example of the latter, I have access to a university library's online research system, and it gives me access to things like Newsbank, Lexis-Nexis, etc. Cross-site scripting is sometimes used while providing that access. Oh, and it shows up when using a lot of Facebook apps.
Anyway, this can be annoying. You can turn it off entirely or try to add exceptions that allow the content you need. I turn it off when I know I'm going to be using the library, for instance, because trying to wade through adding all those exceptions is a chore. NoScript doesn't provide an automated way to do this.
Other than that, it's mostly just building up your whitelist of allow domains. Once you've done that for the sites you visit most often, you tend not to notice it.
|