dgz
Supreme [H]ardness
- Joined
- Feb 15, 2010
- Messages
- 5,838
No, there hasn't been an update to the browser itself. The problem seem to be somewhere on Mozilla's back-end, and apparently affects all add-ons.
Everything was working fine when I went to sleep 7 hours ago. Then I woke up and boom: the web is working normally. I've been browsing with NoScript for nearly a decade so the difference is very noticeable to me. Browsing with JS enabled is a pain: ads, popups, notifications and stuff. It's wrong.
For the time being I'd recommend typing about:config in the address bar, searching for "javascript.enabled" and toggling the option to false.
Alternatively, it may be possible to temporarily disable the signature check until the people across the Atlantic wake up and fix the issue.
Everything was working fine when I went to sleep 7 hours ago. Then I woke up and boom: the web is working normally. I've been browsing with NoScript for nearly a decade so the difference is very noticeable to me. Browsing with JS enabled is a pain: ads, popups, notifications and stuff. It's wrong.
For the time being I'd recommend typing about:config in the address bar, searching for "javascript.enabled" and toggling the option to false.
Alternatively, it may be possible to temporarily disable the signature check until the people across the Atlantic wake up and fix the issue.