Link text disappears on specific website when hovering over with mouse
Categories
(Core :: Layout, defect)
Tracking
()
People
(Reporter: montirever.web, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(7 files, 1 obsolete file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
Website https://www.coingecko.com/ru
Links are hidden when you hover the cursor. Everything works fine on chrome. This bug in all versions of firefox
Comment 1•4 years ago
|
||
Please provide clear and complte steps how to see what you see. I don't see any such dialog when going to
click to the dropdown menu "RUB" or "USD" (at the very top )
and hover over the menu text .
sent you a screenshot from chrome, in firefox this text is painted over on hover
https://prnt.sc/11xie7u
Comment 3•4 years ago
|
||
Thanks. I can reproduce now. Clicking "RUB" does not show any problem. Need to click the "USD" dropdown.
Comment 4•4 years ago
|
||
Hi,
I was also able to reproduce the issue using Nightly 90.0a1 and Beta 89.0b4 on Windows 10, however, it did not occur on Firefox 88.0 (20210415204500) on my end.
Could you please check if it also occurs to you on Firefox 88 in safe-mode? Here is a link that can help you with that:
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_start-firefox-in-safe-mode
I'll set a component in order to involve the development team in reviewing this issue.
Thank you for reporting!
Assignee | ||
Comment 5•4 years ago
|
||
Can we get a regression range Peter? I can't repro, but since it seems you can, that'd be awesome.
Comment 6•4 years ago
|
||
FWIW, I can reproduce this in my Nightly on macOS -- but it's intermittent, which makes it hard to use mozregression with any confidence. Sometimes the issue reproduces, other times it doesn't, even when launching the exact same build. I've seen it happen with a build at least as far back as 81; but I've also seen it NOT happen with an up-to-date build.
When the problem doesn't reproduce, I do generally see the first item hovered "blink" for a moment, like it disappears but then redraws; sometimes I've even had several items disappear, but then pop back into view as I move to hover over another one. Once this initial glitchiness is over, the items seem stable.
Overall, I think this feels more like a painting/graphics issue than a layout bug. Moving to Graphics in the hope someone may recognize the symptoms and have an idea what's going on.
Comment 7•4 years ago
|
||
Turning off display list retaining seems to fix it for me (turning off webrender has no effect).
Comment 8•4 years ago
|
||
regression range
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1f91961bb79ad06fd4caef9e5dfd546afd5bf42c&tochange=c616a6fd5e4b20cca139fcdd3957682afaa862b9
which contains
d5e1ed773fefe2eb9d52402dd74b5fea19b8b4a4 Matt Woodrow — Bug 1416055 - Enable retained display lists for Nightly builds. r=miko
Comment 9•4 years ago
|
||
regression range with retain display lists force enabled
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=515407ebfa1433c31144374313bbfd8b942af41c&tochange=ee21e5f7f1c1726e0ed2697eb45df54cdceedd36
The only thing display list related in there I see is
dd40c8a5af547f1fdb9c37907ba27cb9d5b9d8a6 Matt Woodrow — Bug 1411132 - Always recurse into merging for sub-lists, even when there isn't a matching new item, so that we find all items that need invalidating. r=ethanlin
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
I'm clearing the needinfo request since the regression range was already added.
Thanks Timothy!
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Reduced testcase
Comment 12•4 years ago
|
||
A testcase with timer.
Comment 13•4 years ago
|
||
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
Comment 16•4 years ago
|
||
Comment 17•4 years ago
|
||
Clearing NI since this information is no longer necessary.
Assignee | ||
Comment 18•4 years ago
|
||
As per https://drafts.csswg.org/css-will-change/#will-change.
If any non-initial value of a property would cause the element to
generate a containing block for absolutely positioned elements,
specifying that property in will-change must cause the element to
generate a containing block for absolutely positioned elements.
But in this case the transform property wouldn't apply to the element so
there's no reason to create a stacking-context.
Updated•4 years ago
|
Comment 19•4 years ago
|
||
Comment 21•4 years ago
|
||
Comment 22•4 years ago
|
||
Comment 23•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b2b190564271
https://hg.mozilla.org/mozilla-central/rev/b5a42dba2739
https://hg.mozilla.org/mozilla-central/rev/b7e5812ac00c
Comment 25•4 years ago
|
||
The patch landed in nightly and beta is affected.
:emilio, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 26•4 years ago
|
||
I think bug 1709452 is a safer thing to uplift, wdyt miko?
Updated•4 years ago
|
Comment 27•4 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #26)
I think bug 1709452 is a safer thing to uplift, wdyt miko?
I agree.
Comment 28•4 years ago
|
||
Fixed in 89.0b14 by way of bug 1709452 IIUC.
Description
•