<marquee> causes blurry (grayscale-antialiased) fonts for some elements after it
Reported by
huglovef...@gmail.com,
Apr 4 2017
|
|||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3061.0 Safari/537.36
Example URL:
Steps to reproduce the problem:
1. Open the attached file "bug.html".
What is the expected behavior?
All lines starting with "Div" should be rendered using subpixel antialiasing (the default).
What went wrong?
The last two lines are rendered using grayscale antialiasing which is less sharp than the subpixel stuff.
(The marquee element is rendered in grayscale too but that might be intended.)
The blurriness becomes more noticeable with some fonts, like smaller sans-serif ones.
Does it occur on multiple sites: Yes
Is it a problem with a plugin? No
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 59.0.3061.0 Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0
The bug occurs regardless of the hardware acceleration setting.
I don't really know what it means but I attached a screenshot of what I see in the dev tools.
The composition reasons in the screenshot are:
marquee element:
"activeAnimation"
"willChange"
"div 4 (grayscale)":
"Composition due to association with an element that may overlap other composited elements."
"squashingDisallowed"
"div 5 (grayscale)":
"layerForSquashingContents"
,
Apr 4 2017
,
Apr 4 2017
Able to reproduce the issue on Windows-10, Windows-7, mac-10.12.3 and Ubuntu-14.04 using chrome stable version 57.0.2987.133 and canary 59.0.3061.0 with the below steps 1.Opened provided bug.html file in Chrome 2.Opened Devtools and clicked on layers panel Observed the blurr in Div 4, Grayscale and Div 5, Grayscale. Issue,observed from M58 # 58.0.2988.0.From M30 to M57 the option layers is not available. Marking this as Untriaged to get more inputs from dev team. Please find the attached screen cast for reference. Thanks.
,
Apr 6 2017
,
Apr 11 2017
It's not clear to me why we decide that the 4th and 5th DIVs, but not the 3rd one, get their own layers. Clearly getting the layer is breaking sub-pixel AA, which also shouldn't happen.
,
Apr 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2018
My previous comment was wrong. Forcing the marque into a layer forces the other elements into their own layers and the anti-aliasing is lost. Nothing to be done. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by huglovef...@gmail.com
, Apr 4 2017