High priority Bug: 2.3.2 incompatible with web.de E-Mail

Bug reports and enhancement requests
Post Reply
haraldkn
Posts: 1
Joined: Thu Mar 01, 2012 8:14 am

High priority Bug: 2.3.2 incompatible with web.de E-Mail

Post by haraldkn »

Hi folks!

When I tried to open my e-mail via the normally used web-interface of we.de, I suddenly encountered the following: I could log in, display the headers, but when I clicked on a mail to show its contents: nothing happened. :roll: First, I was going to blame web.de, but their status showed "everything normal". Then I had the idear to deactivate noscript (version 2.3.2), and everything functioned as normal. Can I install an older version of noscript and disable automatic update while you are fixing that bug?

Greetings from Aachen, Germany
Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
User avatar
therube
Ambassador
Posts: 7971
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: High priority Bug: 2.3.2 incompatible with web.de E-Mail

Post by therube »

See if the development build fixes anything?
(Might skip that. Appears the latest #dev is the same as 2.3.2?)

If not, older versions are here, NoScript Updates.

Let us know.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a2) Gecko/20120228 Firefox/12.0a2 SeaMonkey/2.9a2
Tom T.
Field Marshal
Posts: 3620
Joined: Fri Mar 20, 2009 6:58 am

Re: High priority Bug: 2.3.2 incompatible with web.de E-Mail

Post by Tom T. »

It could also be profile corruption or an extension conflict.

Please try creating a clean profile from scratch. Install only NoScript, leaving all the defaults. Do not install anything else in this new profile.
Does the problem still exist? If not, then NoScript is not the culprit. Add back your add-ons, one at a time, until the page breaks again.

This procedure is explained more thoroughly in Standard Diagnostic, except that a clean profile is better than using Safe Mode, because Safe Mode would be using the (possibly corrupt) existing profile.

Also, it is important to find out *why* this happens, so that if it is in our power to fix, all other users of the same site will also be helped.

Greetings from USA.
Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Post Reply