15574 - [FEATURE]losing events to nonmodal dialogs on top of modal dialogs

Status: VERIFIED DUPLICATE of bug 19221

(Core :: XUL, defect, P3)

Description

[Marina Fisher]

System: Solaris 2.5; The browser was built with gcc 2.95.1
Start the browser with mozill-apprunner.sh

1. Edit -> Advanced -> Preferences
2. View Mannual Proxy Configuration
3. None of the text fields are editable. Buttons are not activated either

Comment 1

[Kathleen :Brade]

add [e-mail] since I think he's worked on the prefs dialogs.
Matt--have you completed your work on this dialog?  There doesn't seem to be any
JS attached to the xul.

sujay: reproduce by--
 1) go to Edit menu and pick Preferences
 2) click on Proxies (below Advanced)
 3) click on the radio button for "manual"
 4) click on the View... button next to the manual radio button

Comment 2

[matt]

No this is not finished yet.  The buttons need to be hooked up to the js.
The text field problem has to do with dialogs not working right now.

Comment 3

[buster]

matt says this is a generic dialog problem.  Dan M?

Comment 4

[Dan M]

This looks like a platform-specific problem with the way we're handling events for modal dialogs.
gtk and the Mac appear to be losing events to a non-modal dialog on top of a modal dialog.
This problem will appear to go away when we make the prefs dialog non-modal; a project
which is underway already.  In the meantime, as a workaround, you can easily make the "View"
dialog modal.  Still, a basic problem remains.  I'm adjusting the bug description and scheduling
for M13, though I may have to pull it in closer.

Comment 5

[Peter Trudelle]

mass-moving all m13 bugs to m14

Comment 6

[leger]

Putting [FEATURE]in Summary field for queries.

Comment 7

[Dan M]

*** Bug 24663 has been marked as a duplicate of this bug. ***

Comment 8

[Dan M]

Same bug as 19221. Marking this one a dupe of that one because the steps to 
reproduce mentioned in this bug no longer cause a problem (the prefs dialog is no 
longer modal and the proxies pane has been redesigned.)


*** This bug has been marked as a duplicate of 19221 ***

Comment 9

[sujay]

verified in 1/25 build.