User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0 If I read a encrypted (S/MIME) mail, I'm asked for the password. So I click first with the mouse on the message to read it, then a dialog pops up and asks me for the password. I enter it and press RETURN after that the mouse cursor has changed to drag the message. But I don't want to drag it, I just want to read it. Reproducible: Sometimes Steps to Reproduce: 1. Open a message which is encrypted 2. Enter the password and RETURN 3. Not always: The mouse cursor indicates drag&drop. Actual Results: The mouse cursor indicates drag&drop. Expected Results: Nothing should happen.
I have had this problem since thunderbird 0.7 on linux/gtk2.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
No version was released in the meanwhile, still present in 1.0.6.
You need to log in before you can comment on or make changes to this bug.