Closed Bug 490377 Opened 16 years ago Closed 15 years ago

Incorrectly positioned mouseover event triggered on tooltip close

Categories

(Core :: Widget: Cocoa, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 443178

People

(Reporter: ian, Assigned: smichaud)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.9) Gecko/2009040820 Firefox/3.0.9 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.9) Gecko/2009040820 Firefox/3.0.9 When a tooltip disappears a mouseover event is generated in the owning document (even if the mouse was not over the tooltip window). The location of the event is incorrect. It's often to the left and above the actual mouse location. The relative position appears to be different with different window sizes. This occurs on MacOS X in the most recent Firefox 3.0.x and the most recent Firefox 3.6a nightly. Reproducible: Always Steps to Reproduce: I will attach a self-contained example to demonstrate this bug momentarily.
Attached file Testcase
This testcase shows a trail of mouseover events. If you rest your mouse over a square till the tooltip shows up and then move it to make the tooltip disappear, you'll see an incorrect square turn red (ie: receive the event). If you don't see this at first try resizing your window. As far as I can tell about 900-1000 px wide is a good size to see it.
I could not reproduce this bug using the testcase on Windows and Linux using 3.0 and 3.6 nightlies.
Yeah, I tried on Linux and couldn't repro either. It's not surprising since both the event and menupopup code are heavily platform-specific. I wonder if there's some keyword I should use to get the mac guys' attention...
I can confirm this issue in Firefox 3.0.10 on Mac OS X 10.5.6
I can also reproduce this. It looks like a Cocoa widgets bug.
Status: UNCONFIRMED → NEW
Component: General → Widget: Cocoa
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → cocoa
Assignee: nobody → smichaud
This sounds a lot like bug 443178. Is this fixed now?
As far as I can tell, the attached test case now works correctly Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090819 Minefield/3.7a1pre
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: