Open Bug 1336764 Opened 8 years ago Updated 1 year ago

[e10s] css cursor: url("**some_image**"), auto; changes after mouse movement only.

Categories

(Core :: Layout, defect)

51 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: juwagn, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170125094131 Steps to reproduce: Hello, I set continiously different images with css property cursor: url("**some_image**"), auto; Actual results: But image gets not changed immediatelly but only after next mouse movement. Expected results: The image should be changed as soon as possible when set instead to wait for next mouse movement. Such browsers like Chrome or IE work correctly in this scenario. I use FireFox on Windows, all last versions are affected.
Could you provide a testcase, please.
Component: Untriaged → Layout
Flags: needinfo?(juwagn)
Keywords: testcase-wanted
Product: Firefox → Core
Sounds like maybe we don't trigger the cursor update when the image load completes?
Attached file cursor_bug.html
Works perfect on Chrome, IE11, IE Edge, but FF only when moving mouse around.
In this this attachment cursor_bug.html when cursor changes I output info about so that you see, aha here it must be changed, but on FF it does only while permanently moving the mouse around, if you leave mouse without future moving, the mouse cursor stops to change images.
The timer is set actually to 2 seconds, also cursor should change every 2 seconds.
It doesn't work only with e10s enabled.
Summary: css cursor: url("**some_image**"), auto; changes after mouse movement only. → [e10s] css cursor: url("**some_image**"), auto; changes after mouse movement only.
Possibly you are right, I have enabled e10s but was unsure if that is affecting it.
I confirm, when I forcibly disable e10s, there is no bug then, so only e10s affected.
Hello, the version 57 was released but the bug above is still persisting and very annoying. Removed also FireFox and reinstalled completely on fresh system, nobody took the bug yet. The example was attached 9months ago, reproducable 100%, still reproducable..
Flags: needinfo?(juwagn)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: