conflict with screen hover utilities (xScope, uPointer) results non responsive hover

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
7 years ago
7 years ago

People

(Reporter: echo, Unassigned)

Tracking

6 Branch
All
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-us) AppleWebKit/533.20.25 (KHTML, like Gecko) Version/5.0.4 Safari/533.20.27
Build Identifier: 4.0

When another program that uses global screen hovering such as xScope, is launched with Firefox 4, Firefox's hovers are non responsive to html (links, pseudo class), css or javascript, and cursor stays as ibeam, rather than pointer. Links still work, but there's no visual activation.

Reproducible: Always

Steps to Reproduce:
1. Launch xScope with Firefox 4
2. Firefox 4's hover states are visually non responsive
3. Quit xScope
4. Firefox 4's hover states function normally
Actual Results:  
Firefox 4's hover states are visually non responsive

Expected Results:  
Firefox 4's hover states function normally

Shared reports at https://support.mozilla.com/en-US/questions/793586. I reported this to xScope's iconfactory also, but now suspect it may be Firefox's bug, since it started with a new version of FF, not xScope, and a post from the above link reported similar on Windows, where that couldn't involve xScope, a Mac only app. I suspect a similar type of app is open when this is triggered, that has to do with global screen hovering. I asked for other evidence of a reproducible conflict with another program.
(Reporter)

Updated

7 years ago
Version: unspecified → 4.0 Branch
(Reporter)

Updated

7 years ago
Summary: conflict with xScope results non responsive hover → conflict with screen hover utilities (xScope, uPointer) results non responsive hover
(Reporter)

Comment 1

7 years ago
Another report on the above support.mozilla thread, about uPointer, another utility that effects hover globally.

Comment 2

7 years ago
The problem exists with other applications, such as Samsung mWiMAX adapter management tool on Mac OS X, while application window is open and placed behind the browser's window. ONLY elements, which are exactly at the same position as application window, are affected.

Comment 3

7 years ago
Please please look into this. The problem is still in existence on FF 4.01. Please see related post of the issue: 

https://support.mozilla.com/en-US/questions/793586

Comment 4

7 years ago
I can report/confirm that the problem was introduced with FF 4.0, as FF 3.6 works fine when xScope is used.

Comment 5

7 years ago
I Also confirm the issue was introduced in FF 4.0

Comment 6

7 years ago
This problem still occurs in Firefox 6.0.1 on Mac OS X 10.7. I can also add that neither Chrome (13.0.782.220) nor Safari (5.1) has the same issue with xScope.

I don't know a great deal about how such things work in Cocoa apps, but I imagine there's some difference in the way the mouse events are triggered when a tool like xScope that also captures mouse events is running. Firefox's Mac UI code must be handling this differently to WebKit's.

Comment 7

7 years ago
I have found one fix that works for me and still allows me to have xScope up and running. If i only have loupe active i am able to leave xScope on all the other tools are inactive. When i need the other tools i just activate them using my assigned hot keys.

Now the hover works fine.
(Reporter)

Updated

7 years ago
Version: 4.0 Branch → 6 Branch

Comment 8

7 years ago
For me this bug no longer appears in FF 6.0.2 on Mac OS X 10.6.7
(Reporter)

Comment 9

7 years ago
@Timidfriendly, this is not true for me, testing FF 6.0.2, just having xscope launched causes the hovers to break, with no xscope tools launched, or with just loupe. I need to quit xscope app for FF to function normally.
(Reporter)

Comment 10

7 years ago
Bug as originally reported, still exists for me testing FF 6.0.2 with Mac OS  X  10.6.8

Comment 11

7 years ago
This is also a problem on MacOS 10.6.8, FF 7.0.1, and uPointer 1.1.3.  Everything worked until fine until I moved from FF 3.6.23 to FF 7 3 days ago (don't ask).  Now if I mouseover something like a dropdown list the dropdown does not drop down.  I disable uPointer, click on FF, mouseover the dropdown list, and it works perfectly.  Re-enable uPointer, click on FF, mouseovers fail to operate again.

Safe mode doesn't solve anything.  Booting with the only two programs running on my system being FF and uPointer causes problems, and uPointer doesn't cause a problem in another application I use, so it's safe to say that the conflict is FF<>uPointer.

Helppp!
(Reporter)

Comment 12

7 years ago
Confirmed, bug still present on FF 7 running Mac OS X 10.7.2 with xScope.

Comment 13

7 years ago
Cautiously optimistic that this appears -- after 10 minutes of testing -- to be working in FF 8.0.0 with uPointer active.  However, I don't see anything in the squashed bugs report for 8.0 that appears to show it was resolved.  Did y'all do something about this and forget to tell us?
(Reporter)

Comment 14

7 years ago
Yes!!! FF 8.0 with xScope works, this bug is gone. Running Mac OS X 10.7.2.
I suspect it was fixed "coincidentally" from what @Henry wrote above, and that there was never any dev attention to this report.

I'm marking as resolved, whew!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.