InformAction Forums

I've found out the problem. The workaround does not work if there's an <iframe> with JavaScript inside changing "document.domain". Are there any other ways?

It appears that the workaround works only on zhidao.baidu.com. Other sites still have the same problem. Including: http://guide.opendns.com/?url=www.myfirehost.com&servfail http://web.qq.com (I've modified noscript.surrogate.stickyDomain.sources.) (I will add more when I find more.) Any other wa...

Thanks a lot for the fast response. The code you provided works well. (You added an extra "s" after "surrogate", though.) Is it okay to let NoScript allow execution of inline scripts on a page on "sub.example.com" with JavaScript setting its "document.domain" ...

That expected behavior created a lot of difficulty when I'm trying to visit "http://zhidao.baidu.com". It sets "document.domain" to "baidu.com", so in order to allow inline scripts on the page to execute correctly, I have to allow the whole base 2-nd level domain "...

Environment: Firefox 3.54 (latest when posting) with NoScript1.9.9.14 (latest when posting) on Ubuntu 9.10 Karmic Desktop NoScript detects the domain of a site incorrectly when "document.domain" is set to wrong value with JavaScript. For example, if there's a page on "subdomain.exampl...