290588 - focus on both dialog and menu lost when a dialog box is opened while menu is opened

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Frank]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906

When a menu is opened (only tested with Bookmarks menu so far) and a dialog box
pops up (security ones are the only ones that have happened so far), it is
impossible to click anywhere in the menu to close it, or to click on the dialog
box to close it. The dialog box is focused but is behind the menu. Pressing
space (presumably to close the dialog box) does nothing. Pressing escape closes
the menu and restores clickability on the dialog box.

Reproducible: Always

Steps to Reproduce:
0. Go to a website that requires encryption/security
1. Before the dialog box pops up, click the Bookmarks menu
2. When the dialog box pops up, the bug will occur

Actual Results:  
Exactly what was described in the 'Details' section. If you move the mouse some
items on the bookmarks menu appear to highlight for about 1/2 a second after the
dialog box pops up.

Expected Results:  
Either the dialog should have popped up in front of the menu and gained focus
(to allow the user to click 'OK') or the menu should continue to respond and be
able to close.

Comment 1

[Andrew Schultz]

this works ok (not perfectly, I'm hitting a WM bug) for me with linux trunk
20050416 and 1.7.2 with fluxbox window manager.

What WM are you using?

Comment 2

[Frank]

Additional information - pressing up or down while this happens does move the
selection thingy on the Bookmarks menu.

I'm using KDE 3.4.

Comment 3

[Frank]

And some more information - apparently this does not affect the 'save file'
dialog box (the one with 'open with' and 'save to disk') - I opened the
bookmarks menu before the dialog and nothing bad happened.

Cheers!

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.