I'm trying to go through the steps listed in the official Noscript FAQ and it says:
4.4
Q: Can I bypass Anti-XSS filters for certain web pages?
A: If you're a bit of the "geek" type, you know regular expressions and you're very confident the target web page is immune to XSS vulnerabilities, you can tweak the NoScript Options|Advanced|XSS|Anti-XSS Protection Exceptions rules, i.e. a list of regular expressions (one on each line) used to identify web addresses which you deem do not need to be protected against XSS.
But of course, in the current version of Noscript, there are no XSS options listed under Options|Advanced except for "Sanitize cross-site suspicious requests" and a button to clear all my XSS blacklisted/whitelisted sites. There certainly isn't an entire XSS sub-menu. As far as I can tell there is no way to disable Noscript's XSS filtering, either per-site or at all, except to completely disable Noscript. The FAQ and Features pages also mention some about:config preferences that can be edited to mess with XSS settings, but the current version of Noscript doesn't have any about:config preferences. Searching for "noscript" in about:config yields zero results.4.5
Q: Can I turn off the Anti-XSS protection?
A: Even if it's not recommended for daily usage, temporarily disabling the Anti-XSS protection may be useful, e.g. for testing purposes if you're a security researcher hunting for XSS vulnerabilities. To do that, you just need to open NoScript Options|Advanced and toggle the cross-site restrictions preferences.
So how do I get this kind of cross-site content working in the current version of Noscript? And also, is the developer likely to see this post and update the FAQ and Features pages, or should I file a bug report somewhere about the outdated website info?