Closed Bug 40454 Opened 25 years ago Closed 25 years ago

Event problems during display of profile wizard

Categories

(Core :: XUL, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: slogan, Assigned: bryner)

Details

(Whiteboard: [nsbeta2+][dogfood-])

Bringing up part of the profile wizard requires that the mouse be wiggled in order for wizard dialogs to show up. Steps (provided by jwbaker@acm.org): Reliably reproduceable here. Steps: + + 1) rm -rf ~/.mozilla + 2) cd package + 3) ./mozilla -installer + 4) Click "Manage Profiles" + 5) Select "jwb" (your username instead) + 6) Click "Start Mozilla" + 7) Wiggle the mouse (that's another bug) For me, the steps to see this when creating a new profile are nearly the same, except step 5 I select the "Create New Profile" button and have to wiggle the mouse in order to get the next dialog in the wizard to popup.
Nominating dogfood because this indicates a problem in our basic infrastructure, and a product that requires a user to wiggle the mouse in order for dialogs to appear is not dogfood ready.
Severity: normal → critical
Keywords: dogfood
I think this is a duplicate of bug #35284 'onClick fires on blur, not button up'. Anyone agree?
I don't agree on the duplicate, because I can't reproduce Bug 35284 on the same build that I see this bug. Besides that, I think this bug is more appropriately prioritized.
Putting on [nsbeta2+][dogfood-] radar. Does not need a fix ASAP for daily work, but we should fix this for beta2.
Whiteboard: [nsbeta2+][dogfood-]
danm and i are working on this.
The problem is understood here, we're just trying to make sure the fix doesn't break anything else.
reassigning to bryner since he knows more than I do about this
Assignee: blizzard → bryner
This is now fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified fixed linux 2000060608 rh6.1
Status: RESOLVED → VERIFIED
Adding keyword to bugs which already show a nsbeta2 triage value in the status whiteboard so the queries don't get screwed up.
Keywords: nsbeta2
You need to log in before you can comment on or make changes to this bug.