Closed Bug 30906 Opened 25 years ago Closed 24 years ago

Putting Mozilla into bg then fg causes :hover to stop working

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
PowerPC
All
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: mikepinkerton, Assigned: saari)

Details

- launch apprunner up to the profile selection dialog
- click in the finder to put it into the background
- bring the profile mgr back to the fg

expected results:
- all rollover feedback still works

actual results:
- no rollover feedback works on _any_ titled button, even once navigator comes 
up. opening new windows doesn't fix it.

it appears we get into a state where the event state manager is confused and 
refuses to process :hover rules.
this really sucks. beta1.
Keywords: beta1
Wouldn't this be a saari issue?
Summary: Putting Mozilla into bg causes :hover to stop working → Putting Mozilla into bg then fg causes :hover to stop working
oh, i forgot to mention that scrollbars don't work in this state either. makes it 
pretty damn hard to use the product.

I can't reproduce this, given the steps above. Does having the console window 
around (i.e. debug build) make a difference?

it might. are you only trying to repro it with an optimized build?

No, my debug build. I have seen mozilla get into this state, but I think the 
steps to cause it are more complex, or timing related.

I've found (after a little more searching) that it only happens when I use 
DragThing to bring mozilla to the fg. the app menu or clicking in window doesn't 
break it. removing beta1, as this now seems a bit contrived, but I'm still 
worried what could be so different.
Keywords: beta1
reassigning to saari for triage.
Assignee: trudelle → saari
How does DragThing bring things to front? Does it send an activate or something 
more evil with the window list?
Status: NEW → ASSIGNED
Target Milestone: M15
pink, this works fine for me with DragThing 2.7



What version are you running?


hardly critical, changing severity to normal, moving to m17
Severity: critical → normal
Target Milestone: M15 → M17
Mass moving M17 bugs to M18
Target Milestone: M17 → M18
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
This works on 8.6 for the main windows, is it wfm, or 9.0, or just PM?  In any
case, it is ->future.
Target Milestone: M21 → Future
Pinkerton says this is WorksForMe now
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
OS: All
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.