487424 - Mouse-Click is disabled in POP-3 Authentication

Status: RESOLVED INCOMPLETE

(Thunderbird :: Mail Window Front End, defect)

Description

[Stewart Dickson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8
Build Identifier: 20090407032555 Shredder version 1.9.1.3383

I have two POP-3 accounts created in my Shredder installation.  One account's server operates SMTP via SSL encryption, the other does not.  The account which does SMTP over SSL is ORDERS OF MAGNITUDE SLOWER on a 2.4GHz Core2-Duo running Win32XP-Pro THAN MY HOME 300MHz G4 PowerPC running MacOS-X 10.4.*.  On WinXP, the interaction between the two account authentication dialogs totally step on each other.  (On MacOS, they each come up individually.  The second one doesn't come up until the first has dismissed.)  This morning, I am sitting here looking at two authentication dialogs that won't respond to mouse-clicks.  They are only responding to the keyboard.  Initially, I couldn't even move the cursor to the Windows toolbar to bring up FireFox to write this report.  I had to launch FireFox via Google Desktop -- with double-<ctrl>.  Maybe Google Desktop is the problem rather than the solution?  Who knows?  Windows has to be the most-abused OS on the planet.  They wrote it this way because the 3rd-party developers demanded it.  Every application needs to be THE ONLY APPLICATION YOU WILL EVER NEED.  Every application wants to take over your computer.  The Web Browser has become its own goddam operating system.  It's Boyle's Gas Law of software -- the software expands to occupy all available hardware.  This is idiotic.  And Windows is absolutely the most idiotic.  It has to stop somewhere.

Reproducible: Sometimes

Steps to Reproduce:
1. A new version of Shredder is available... installing and will re-start...
2. Shredder starts.  First account authentication dialog comes up. I begin to move it to the edge of the screen.
3. Second account dialog comes up and grabs mouse focus away from the first dialog.  I type in my p*sswd, but can't click [OK].  But, I find that I can <tab> over to [OK] and send the dialog with <Enter>.
Actual Results:  
All of the above moves in glacial, geologic time.  I swear to God, WinXP has to weld an authentication dialog to the network interface with atomic operations in order to do SMPT over SSL with authentication.  Nothing else on the computer can move.  It is Conservatism that has brought us here -- Fear feeds the need for Security.  And Windows has so many hooks allowing you to do Evil Things deep in the OS that it has rendered itself incapable of moving.

Expected Results:  
On MacOS-X, I can deal with the first authentication dialog, it will dismiss, than I can deal with the second dialog in sequence.  In WinXP, I am constantly typing the second half of the first p*sswd into the second dialog because it has wrested focus control.  This is not to say that MacOS applications are free of focus control issues.  There are instances in which you have to click on the toolbar of the top-level, parent window before you can get focus in the dialog.  But, MacOS is definitely much less painful.

Comment 1

[Joshua Cranmer [:jcranmer]]

As best as I can discern from your... unorthodox bug report, this should be a dupe of bug 338549. Would this be correct?

Comment 2

[Stewart Dickson]

(In reply to comment #1)
> As best as I can discern from your... unorthodox bug report, this should be a
> dupe of bug 338549. Would this be correct?

As I read it, bug 338549 is the first part -- but it has gotten worse as now
mouse-clicks don't get to the authentication dialogs, only keystrokes.  I believe that this behavior is new. Thanks, -Stewart

Comment 3

[Joshua Cranmer [:jcranmer]]

If you have only one server request the authentication, do you still have the hanging problem?

Comment 4

[[:Aureliano Buendía]]

Reporter can you reply to comment #3?

Comment 5

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.