Open Bug 1736993 Opened 4 years ago Updated 2 years ago

The new mouseover hand mousepointer is a bug, a true annoyance, get the old one back please! Tempted to switch to Chromium or even Edge!

Categories

(Core :: Widget: Gtk, enhancement)

Firefox 93
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: arnoldvanh, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

Mouseover

Actual results:

Left pointy hand appears instead of the trusted right up version

Expected results:

Look at other browsers, a normal hand pointing UP should appear.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Security' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → DOM: Security
Product: Firefox → Core
Component: DOM: Security → Widget: Gtk

Is that a recent regression?

Flags: needinfo?(arnoldvanh)

Please try to find a regression range (pushlog URL). For example:
$ pip3 install --user mozregression
$ mozregression --good 2021-01-01 --bad 2021-10-20 -a https://example.com

I don't care if it is a regression, please make it at least configurable with settings or something.
Thanks.

Flags: needinfo?(arnoldvanh)
Flags: needinfo?(arnoldvanh)
Flags: needinfo?(arnoldvanh)

(In reply to arnoldvanh from comment #4)

I don't care if it is a regression

This is a community-made browser.
Either you help, or it won't be fixed. I don't have this problem, the correct cursor (finger pointing up) is displayed.
Please try to find a regression range. Which Linux distribution, version and desktop environment are you using?

Flags: needinfo?(arnoldvanh)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug doesn't have a severity set, could you please set the severity or close the bug?

For more information, please visit BugBot documentation.

Flags: needinfo?(arnoldvanh) → needinfo?(stransky)
Flags: needinfo?(stransky)
You need to log in before you can comment on or make changes to this bug.