Closed Bug 15353 Opened 21 years ago Closed 21 years ago

[PP] Can't get focus in Pref UI

Categories

(SeaMonkey :: Preferences, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: paulmac, Assigned: pavlov)

References

Details

Attachments

(1 file)

I am unable to get focus in the Pref UI using the 100108 Linux M11 build. The
only way to close it is to the the X in the upper right hand corner, and you
can't modify any Prefs at all. To reproduce:

1. Open up Preferences via the Edit menu.
2. Try clicking anywhere in the PrefUI

Results: Nothing happens. You must close Prefs with the X.

This does not occur on Windows build. Mac not tested. Marking PP.
Assignee: matt → pavlov
This seems more of a general Linux issue. I'm having the same problems getting
focus on password dialogues also. Can't click OK on them either. Will try pavlov
on this one :-)
An easy way to duplicate the password focus issue:
1. Goto slip/projects/marvin/wallet/login.html
2. Enter a signon and click Login
3. Enter password, and again when prompted
4. Goto Edit - Wallet - Change Password

Results: You cannot get focus on the change password dialogue and must click on
the X to close it.
*** Bug 15362 has been marked as a duplicate of this bug. ***
Priority: P3 → P2
Target Milestone: M11
This is hindering pref work.
This is in the M10 builds. Do we really want to ship M10 with this nastiness?
modeless prefs dialog would workaround this problem :-)
posting a patch.
Target Milestone: M11 → M10
Putting on m10 radar so we can think about this for m10.
was this fixed today.. err.. yesterday?  (i really should sleep) by danm's
checkin?
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
danm has checked in a fix for bug 15596 to the m10 branch.
should appear in the next respin
Status: RESOLVED → VERIFIED
verified
Bulk move of all Pref UI component bugs to new Preferences component.  Pref UI 
component will be deleted.
Component: Pref UI → Preferences
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.