window mouseout events aren't fired when the mouse leaves the windows by the sides.

RESOLVED FIXED

Status

()

Core
Widget: Cocoa
P2
normal
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Oliver Hunt, Assigned: Josh Aas)

Tracking

({testcase})

Trunk
PowerPC
Mac OS X
testcase
Points:
---
Bug Flags:
blocking1.9 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-us) AppleWebKit/523.10.3 (KHTML, like Gecko) Version/3.0.4 Safari/523.10
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2

If a mouseout listener is attached to the window object, it will not fire if the mouse leaves through the sides of the window.

The only way to trigger the mouseout is if the mouse touches the chrome.

Reproducible: Always

Steps to Reproduce:
1. attach a mouseout listener to window
2. move the mouse out of the window without touching the chrome
Actual Results:  
The mouseout listener doesn't fire

Expected Results:  
the mouseout listener should fire.
(Reporter)

Comment 1

11 years ago
Created attachment 293073 [details]
Simple test case

Here's a nice and simple testcase :D

Updated

11 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
This started happening with the 2007-12-06-04-trunk nightly, so it's
likely to be fallout from the patch for bug 406362.

And it may be fixed by the patch for bug 407876 (not yet landed).

(It doesn't happen on Windows.)
Assignee: nobody → joshmoz
Component: DOM: Events → Widget: Cocoa
QA Contact: events → cocoa
Version: unspecified → Trunk
(Assignee)

Updated

11 years ago
Flags: blocking1.9+
Priority: -- → P2
(Assignee)

Comment 3

11 years ago
Yes, this is fixed by the patch in bug 407876.
Depends on: 407876
(Assignee)

Comment 4

11 years ago
bug 407876 landed, this is fixed
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.