Closed Bug 371116 Opened 18 years ago Closed 18 years ago

Focus is not transferred when using mouse autoraise

Categories

(Core :: DOM: Events, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 372177

People

(Reporter: ryukbk, Unassigned)

Details

(Keywords: regression)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070221 Minefield/3.0a3pre ID:2007022101 [cairo] 1. Enable X-mouse autoraise in Windows XP by http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx 2. Create http://slashdot.org/ in the Bookmark Toolbar Folder 3. Close FF 4. Open FF 5. Push the button in the bookmark toolbar to open Slashdot 6. File | New Window 7. Move the mouse cursor to the first window and move the focus onto it from the new window created in 6 8. Push the button in the bookmark toolbar in the first window to open Slashdot Expected: The first window opens Slashdot What I get: The second window opens Slashdot Actually I see other wierdness such as PageDn/Up key moves the second window / can't edit the editbox in the first window etc. but they are all caused by malfunctioning focus.
Product: Firefox → Core
QA Contact: general → general
This build works as intended. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070220 Minefield/3.0a3pre ID:2007022005 [cairo] Today's build is still broken.
Summary: Focus gets sticky when using mouse autoraise → Focus is not transferred when using mouse autoraise
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070303 Minefield/3.0a3pre ID:2007030313 [cairo] The resulting behavior in the comment #1 seems to have changed slightly in this build or an older build, the second window gets raised when opening a new page from the bookmark tool bar in the first window.
Fixed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070310 Minefield/3.0a3pre ID:2007031021 [cairo]
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2) > The resulting behavior in the comment #1 seems to have changed slightly in this > build or an older build FWIW, this change could be the result of bug 371564 patch !?
Component: General → DOM: Events
Keywords: regression
You need to log in before you can comment on or make changes to this bug.