Closed Bug 5815 Opened 26 years ago Closed 25 years ago

[PP] Incorrect menu assigned to window if focus changes before window appears

Categories

(Core :: XUL, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: elig, Assigned: saari)

References

Details

* TITLE/SUMMARY [PP] Incorrect menu assigned to window if focus changes before window appears * STEPS TO REPRODUCE 0) Launch Apprunner 1) From the Bookmarks menu, select Manage Bookmarks… 2) Before the Bookmarks window actually appears, *quickly* click on the browser window, making it the active window. * RESULT - What happened The browser window inherits the same menu bar that the Manage Bookmarks window has. Chris Saari notes that this is a result of a race condition, and is more likely to be noticed on a slower machine. - What was expected Correct menu/window pairings, despite any nefarious activity while Apprunner is conjuring up the window. ;) * REGRESSION - Occurs On Mac OS Apprunner (4.30.99 optimized build) - Doesn't Occur On Win32 Apprunner (4.30.99 optimized build [NT 4, Service Pack 3]) Linux Apprunner (4.30.99 optimized build) * CONFIGURATIONS TESTED - [Mac] Power Mac 8500/120 (233 Mhz 604e), 64 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.5.1 - [Win32] Vectra VL (233 Mhz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP3. - [Linux] Vectra VL (266 Mhz P2), 96 MB RAM.
QA Contact: 4078 → 1698
[QA Assigning to self and CC:ing Phillip. Phillip, if you have a burning urge to be the QA Assigned on this bug, please alter as desired.]
Target Milestone: M10
This is difficult to repro on faster machines, so I'm placing it at M10
Status: NEW → ASSIGNED
I'm having trouble hitting the timing window here and reproducing on my G3 300, is there a slower machine I may work with that can repro this better?
Target Milestone: M10 → M11
Not going to have time in M10, and this isn't high priority. Moving to M11
Blocks: 12673
Blocks: 12670
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I keep trying to rep this and cannot on various machines... unless someone can show me a machine that still exhibits this behavior, I'm marking works for me
Status: RESOLVED → REOPENED
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: WORKSFORME → FIXED
Status: RESOLVED → VERIFIED
Hey, Chris --- I just spent about 20 minutes trying to reproduce this using a 120 Mhz 604 (8500/ 120), with this morning's build. I believe that it's fixed. With pre-emptive apologies for anality, I'm also re-opening this bug and changing the resolution to Fixed, as the bug appears to have had a mystery fix.
You need to log in before you can comment on or make changes to this bug.