Open Bug 1259930 Opened 9 years ago Updated 1 year ago

[e10s] Large CSS custom cursor flickers when moving it

Categories

(Core :: Widget: Win32, defect, P3)

Product:
Core
Component:
Widget: Win32
Version:
46 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
e10s + ---
firefox45 --- unaffected
firefox46 --- wontfix
firefox47 --- wontfix
firefox48 --- wontfix
firefox49 --- wontfix
firefox50 --- fix-optional
firefox51 --- fix-optional

People

(Reporter: epinal99-bugzilla2, Unassigned)

References

Details

(Keywords: regression)

Attachments

(2 files)

wand128.png
(deleted), image/png
Details
testcase.html
(deleted), text/html
Details
Attached image wand128.png (deleted) —
Found when testing https://bugzilla.mozilla.org/show_bug.cgi?id=1253573#c1 STR: move the mouse cursor inside the "128 x 128 px" div. http://www.ivank.net/veci/cursors.html Result: custom cursor flickers. Regression range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7e2e9a6c0f0fe1f84b55987afcdc01fb16a124a3&tochange=3f4b6a6542ec6be9689ae265db6db4391c7d79d8 Jim Mathies — Bug 1222662 - Disable cursor caching in the content process on Windows. r=aklotz
Attached file testcase.html (deleted) —
Blocks: e10s, 1222662
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox45: --- → unaffected
status-firefox46: --- → affected
status-firefox47: --- → affected
status-firefox48: --- → affected
tracking-firefox46: --- → ?
tracking-firefox47: --- → ?
tracking-firefox48: --- → ?
Flags: needinfo?(jmathies)
Keywords: regression
I do see a little bit of flicker in this test case. We should take a look at this.
Flags: needinfo?(jmathies)
aklotz, your regression. any ideas?
Flags: needinfo?(aklotz)
(In reply to Doug Turner (:dougt) from comment #3) > aklotz, your regression. any ideas? I was just the lowly reviewer, I swear!
Flags: needinfo?(aklotz)
tracking-e10s: ? → +
Priority: -- → P3
Tracking for 49, if anyone fixes this please request uplift so we get it into 48 too.
status-firefox49: --- → affected
tracking-firefox48: ? → ---
tracking-firefox49: --- → +
Just circling back on this bug - we're tracking for 49 but right now no assignee - Jim do you plan to own this bug? Thanks.
Flags: needinfo?(jmathies)
(In reply to Marcia Knous [:marcia - use ni] from comment #6) > Just circling back on this bug - we're tracking for 49 but right now no > assignee - Jim do you plan to own this bug? Thanks. No it's currently an e10s tracking + P3 so non-blocking, lower priority.
Flags: needinfo?(jmathies)
Hi Jim, May I know is there any plan to fix this in 49?
Flags: needinfo?(jmathies)
(In reply to Gerry Chang [:gchang] from comment #8) > Hi Jim, > May I know is there any plan to fix this in 49? No there is not. This is polish work tied to e10s, currently a p3.
status-firefox49: affected → wontfix
status-firefox50: --- → fix-optional
status-firefox51: --- → fix-optional
tracking-firefox49: + → ---
Flags: needinfo?(jmathies)
Also I can't reproduce, are people still seeing this?
(In reply to Jim Mathies [:jimm] from comment #10) > Also I can't reproduce, are people still seeing this? Yes, on Win 7 x64 with the latest Nightly, it's still visible.
(In reply to Loic from comment #11) > (In reply to Jim Mathies [:jimm] from comment #10) > > Also I can't reproduce, are people still seeing this? > > Yes, on Win 7 x64 with the latest Nightly, it's still visible. Hmm, that's what I'm testing on and I don't see a flicker issue. I wonder if this is tied to graphic cards in some way.
Severity: normal → S3
Component: General → Widget: Win32
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: