Closed Bug 325558 Opened 16 years ago Closed 14 years ago
Mouse cursor disappears if hidden by Flash against the side of the window
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:184.108.40.206) Gecko/20060201 Camino/1.0b2+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:220.127.116.11) Gecko/20060201 Camino/1.0b2+ the pointer disappears, and not just within the browser, but outside of it... Reproducible: Always
I see the same thing happen on the bottom bird, too, but as soon as I mouse out of the Flash animation there in the sidebar, the cursor comes back. Even if I leave the cursor there and cmd-tab into another app, the cursor comes back immediately. cl
Does this happen in Firefox 18.104.22.168 or Safari?
dunno about firefox, but it doesnt happen w/ safari.
In Fx, I can generally (but not always) get the cursor back if I mouse out of the window to the top or the left of the plugin, and alwsys get it back if I mouse out to the bottom or to the right, back over the text. In Cm, the only sure way to get it back is to mouse out over the text; sometimes I can get it back by mousing out over the bottom of the plugin, but never via the top or the left sides.
Component: Accessibility → Plug-ins
This is a dup, but I can't find the original.
Simon, are you thinking of https://bugzilla.mozilla.org/show_bug.cgi?id=260617#c12 ?
Yes. Not sure why bug 260617 was marked as WFM
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: The pointer disappears when I select the top bird on the menu (click on the graphic on the main page to get the pop up window that contains the menu) → Mouse cursor disappears if hidden by Flash against the side of the window
Priority: -- → P2
Target Milestone: --- → Camino1.1
Assignee: mikepinkerton → nobody
Severity: major → normal
QA Contact: plugins
Target Milestone: Camino1.1 → Camino2.0
I think this is one of the more serious bugs, and begs for a pre 2.0 designation.
Target Milestone: Camino2.0 → Camino1.1
*** Bug 359376 has been marked as a duplicate of this bug. ***
Target Milestone: Camino1.1 → Camino2.0
Works in FF2, not in trunk Firefox; -> Cocoa widget.
Assignee: nobody → joshmoz
Component: Plug-ins → Widget: Cocoa
Priority: P2 → --
Product: Camino → Core
QA Contact: plugins → cocoa
Target Milestone: Camino2.0 → ---
Version: unspecified → Trunk
Is this a particular symptom of bug 379413, or really a separate bug? Per comment 10, this is a regression for Firefox.
I found this bug today while visiting the following page under OS X: http://arthurmebius.com/ It's really annoying that the mouse pointer is hidden and you have to Cmd+Tab out of Firefox to get the mouse cursor back. This happens with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5pre) Gecko/2008030804 Minefield/3.0b5pre ID:2008030804. Asking for blocking1.9 to hopefully get rid of this regression from switching to Cocoa.
Hardware: Macintosh → All
As additional note you also get back the cursor when leaving the website over the tabbar and Bookmarks Toolbar.
Comment on attachment 314423 [details] [diff] [review] fix v1.0 r=smorgan
Attachment #314423 - Flags: review?(stuart.morgan) → review+
Attachment #314423 - Flags: superreview?(vladimir) → superreview+
Comment on attachment 314423 [details] [diff] [review] fix v1.0 This is a pretty safe bug fix for something that can be pretty frustrating for users. I recommend taking this for RC1.
Attachment #314423 - Flags: approval1.9?
Comment on attachment 314423 [details] [diff] [review] fix v1.0 a1.9=beltzner
Attachment #314423 - Flags: approval1.9? → approval1.9+
landed on trunk
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9pre) Gecko Minefield/3.0pre ID:2008040922
Status: RESOLVED → VERIFIED
This caused bug 496601, because plug-ins are NOT the only widgets we have around. I'm not sure why this was considered "safe" exactly... I'm also not sure why the patch is resetting the cursor, not just unhiding it. How did carbon widgets handle this situation? They didn't have this bug, or bug 496601.
You need to log in before you can comment on or make changes to this bug.