graphical cursor affects the z-index on elements with 3d transformation (with preference: accessibility.browsewithcaret=true)
Categories
(Core :: Web Painting, defect, P3)
Tracking
()
People
(Reporter: hunboy, Assigned: mikokm)
References
Details
(Keywords: regression)
Attachments
(5 files)
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
I can't reproduce any issues with images "blinking" locally, for what its worth. I tried the attached testcase as well as http://jsfiddle.net/utasir/7zn3feLs (the demo shown in the screencast). I tested using Nightly on Linux, as well as Firefox 64 on Windows 10 via BrowserStack.
I wonder if this might be a graphics driver bug?
Updated•6 years ago
|
Comment 4•6 years ago
|
||
For reference, here's a screencast of me trying to reproduce with BrowserStack "remote" windows 10 + Firefox 64. In the screencast, you can see my cursor moving around, and I'm intermittently clicking (on & near the image), but I can't reproduce any blinking-away issues.
Comment 5•6 years ago
•
|
||
hunboy, would you mind going to about:support and copypasting the "Graphics" section into a text file & posting that as an attachment here? [EDIT: never mind about this, comment 6 seems to be a better diagnostic]
There's a chance some graphics-knowledgeable folks (not me) might be able to glean some information about possible sources of trouble from that, or at least figure out correlations perhaps.
Comment 6•6 years ago
|
||
I can reproduce this if I set accessibility.browsewithcaret=true, but not without (since there's nothing editable, and no caret).
Reporter | ||
Comment 7•6 years ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #6)
I can reproduce this if I set accessibility.browsewithcaret=true, but not without (since there's nothing editable, and no caret).
I can confirm this idea, when I turn it to false, the bug disappears.
Reporter | ||
Comment 8•6 years ago
|
||
Reporter | ||
Comment 9•6 years ago
|
||
Mozregression result:
with preference: accessibility.browsewithcaret=true
Last good: 2015-10-23
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0625c68c0abcfe4d10880d15d8fe7d06df3369c9&tochange=d53a52b39a95dced722cca90ac74529b66dd5253
First Bad: 2015-10-24
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0625c68c0abcfe4d10880d15d8fe7d06df3369c9&tochange=26078ba1c7be11cf46706216cad8603b92335cd0
Reporter | ||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
Given the regression range (the smaller one in the lower link in comment 9): hunboy suggests (and I agree) that this seems likely to be a regression from bug 1214212:
e19090d182fa Thinker K.F. Li — Bug 1214212 - Remove clips from separator transform items. r=roc
https://hg.mozilla.org/mozilla-central/rev/e19090d182fa
--> marking as such
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 11•6 years ago
|
||
:miko, can you comment to the bug? Since you worked for css3d, thanks.
Assignee | ||
Comment 12•6 years ago
|
||
I think this problem is caused by caret item causing the content to be wrapped in nsDisplayWrapList, which causes us to create a transform separator1 for the transformed content.
Assignee | ||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Updated•6 years ago
|
Comment 16•6 years ago
|
||
Verified - Fixed on latest Nightly 66.0a1 (2019-01-28) (64-bit) on Windows 10, Ubuntu 16.04 and Mac OS 10.14.
Description
•