-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flickering of <a>
(link) element with transition: all
#724
Comments
I've noted it on July 13th, if this will be of any help. |
This is quite odd yet #723 appears to report the same thing. I think what's happening is 10ten's mousemove handling is flushing style. |
I still need to dig into this further, but at a quick glance, it looks like 10ten does indeed flush style in its mousemove handling. However, as far as I can tell, it has been doing that for years. I wonder if something changed in the user agent stylesheet for Arch Linux that simply makes it more noticeable now. |
This comment has been minimized.
This comment has been minimized.
This has nothing to do with Arch Linux. I have tested it now with Firefox 87.0 (64 bit) on Windows 10 (VirtualBox): exactly the same flickering. |
Right, I can reproduce it on Windows too. I'm just trying to make sense of the fact that I received two bug reports for roughly the same issue within hours of each other: one from an Arch Linux user and one from someone browsing the Arch Linux download page! The good news is I can't reproduce on a commit on 1 Jan 2021 so I am currently bisecting the regression range. So far it looks like it goes back pretty far -- somewhere between the start of April and the end of May. |
Well, coincidence? I have already said that
EDIT: For what it is worth, Arch Linux is quite popular, even more so Arch Linux Wiki. |
Unfortunately it looks like aa8209b is to blame. That patch makes us toggle the |
Fixed by 1dead87 |
Version 1.2.2 was released yesterday so this should be fixed now. |
@birtles, Thank you for notification! Well, what can I say, it is better now. The behaviour is still present on my side, for example, when I quickly move the cursor through such page: Document Body<body>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
<a class="test" href="#">This is a link.</a><br>
</body> |
@sakkamade Thank you for checking! I'm having trouble noticing any difference with that test case between when the add-on is enabled vs when it is not. I've confirmed that in that test case we're not triggering the "covering link" behavior so it must be a separate issue. If there's some more reliable means to reproduce it then I'd be glad to hear it! |
I wonder if there are more reliable. 10ten.mp4EDIT: Yes, it is interesting. It can be seen only when I move the cursor from the top to the bottom, and not when I move it from the bottom to the top. EDIT2: And yes, it also works as expected when I move the cursor from the left to the right and from the right to the left. EDIT3: And I can reproduce it under Windows 10, Firefox 87. |
<a>
(link) tags with transition: all
<a>
(link) element with transition: all
@birtles, So can it be reopened, then? |
Hi @sakkamade, I had a look at the new test case and it looks like those links are stacked so close together that they end up overlapping each other, triggering the "link uncovering" behavior that causes flicker. If you set I think the flicker is an unfortunate but necessary side effect of the (very useful) link uncovering behavior. It could be optimized further but I don't think it's worth it. Please let me know if there is specific content in the wild where this is causing problems and I'll be happy to look into it. |
Right, this is certainly true, in this case, I am unable to replicate the circumstances for reliable reproduction with original content, but I am mostly certain that it is caused by something similar to this:
|
Thanks for following up on this and providing a test case too! I'm more than happy to look into it when there's some real content that's significantly affected by it, but until then I'm afraid I'm not convinced it's worth spending time on. I'm happy to review a PR though if you'd like to look into it further. |
So far I've seen none.
No, this is as far as I will. Oh well. Thank you. |
Active Rikaichamp (however it's named now) causes a flickering transition of
<a>
html-tag.Tested on Firefox 91.0 (64-bit)
Rikaichamp 1.2.1 (Although was experiencing this for quite a while—month since I noticed? Had no idea that this add-on is at fault.)
Arch Linux.
Test document
P.s.
transition: border-color
solves it.The text was updated successfully, but these errors were encountered: