Thrawn wrote:OK, but has the Mycroft project changed? Which sites are being blocked when you go there?
Nothing has changed that I can see. I'm usually on the site about once a month. The only thing that's different is I'm using a more recent (latest) dev build of NoScript, and I'm getting a pile of NoScript-related errors (noscriptService.js) in the Error Console. I have to assume it's NoScript that has the problem, and not Firefox nor the Mycroft site. And I'm not blocking anything at all. All page elements are being served from mozdev.org (or, I assume, mycroft.mozdev.org specifically).
I do use ABE with the default SYSTEM rule set:
- # Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
There are no errors being reported by NoScript itself. There are no ABE errors. There are no ClearClick warnings. There are no XSS warnings. All I have to go on is Firefox horking an error every few seconds on noscriptService.js. Disabling the obvious content blockers (ABP + Ghostery) changes nothing.
I can visit the same results page in Chrome (wherein I am also using the Ghostery and AdBlock plugins, with the same block lists), plus default-deny JS. (JS is enabled for [.*].mozdev.org, same as in NoScript on Firefox.)
When I attempt to add the same—or any—search engine in Chrome, Mycroft happily serves up search plugin information, and I can add the engine in Chrome. Opera also experiences no problems on the Mycroft site, also using ABP and Ghostery.