background-clip: text that is animated onto the page by a parent container is invisible until forced redraw
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
People
(Reporter: aaritak, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36
Steps to reproduce:
I've made a JSFiddle to reproduce this bug.
https://jsfiddle.net/82qmfn9u/
- Create a wrapper element with a text element inside it.
- Give the text element background-clip: text.
- Transition the parent element off screen, then back on.
Actual results:
The text will be invisible until a redraw is forced (either by changing other CSS or switching tab)
Expected results:
The text should be visible.
![]() |
||
Updated•5 years ago
|
Updated•5 years ago
|
![]() |
||
Comment 1•5 years ago
|
||
I can only reproduce the issue if Webrender is Enabled on Windows10 .
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0e0e9c22321ed9f284744cfeb3507710b2d5d606&tochange=9163b1b1da061853f0c34b2725937cbca6975def
Comment 2•5 years ago
|
||
Thanks Alice, nice catch!
Comment 3•5 years ago
|
||
I can reproduce on Linux, with the variation that the text only appears upon first draw. If you hit the toggle button twice, then the text does not appear.
Comment 4•2 years ago
|
||
Is this still an issue? (I tested it and it appears to not have the issue above, but the behavior is different than when I test it in chrome).
Reporter | ||
Comment 5•2 years ago
|
||
(In reply to Glenn Watson [:gw] from comment #4)
Is this still an issue? (I tested it and it appears to not have the issue above, but the behavior is different than when I test it in chrome).
Here's an updated fiddle that actually works for comparing the difference between Firefox and Chrome (which still requires -webkit-
): https://jsfiddle.net/ChiriVulpes/zpq6r7cx/2/
I can't reproduce anymore, not sure when it was fixed. I believe this bug can be safely closed.
Comment 6•2 years ago
|
||
Great, thanks for checking.
Description
•