Why not? In every conceivable use case, the dialog is going to be user-initiated (application startup, surfing to a site or opening a tab or window consciously). In user-initiated situations I don't see a real problem in blocking the entire application for access to an application wide facility.
While I agree right away that window-modal would be better, I would argue it an option to go for a relatively simple solution in 3.0.1 and then fix it better in 3.1 or 3.5. The current problems are worse than the backlash of the quick fix, being that a user cannot continue browsing in a window he wasn't using anyway at the time it popped up.
Also - would the other window block until you also opened a protected site there? In a mutex solution it would only block threads *also* accessing the central password storage, wouldn't it? Again, I'm not familiar with the Firefox code internals, but that's my base assumption here.
Why not? In every conceivable use case, the dialog is going to be user-initiated (application startup, surfing to a site or opening a tab or window consciously). In user-initiated situations I don't see a real problem in blocking the entire application for access to an application wide facility.
While I agree right away that window-modal would be better, I would argue it an option to go for a relatively simple solution in 3.0.1 and then fix it better in 3.1 or 3.5. The current problems are worse than the backlash of the quick fix, being that a user cannot continue browsing in a window he wasn't using anyway at the time it popped up.
Also - would the other window block until you also opened a protected site there? In a mutex solution it would only block threads *also* accessing the central password storage, wouldn't it? Again, I'm not familiar with the Firefox code internals, but that's my base assumption here.