Issue metadata
Sign in to add a comment
|
Background-image with SVG text renders illegibly on Windows in Chrome 60
Reported by
d...@masterleep.com,
Aug 9 2017
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8 Steps to reproduce the problem: 1. Open the blocky.html reduced text case on Windows 7. 2. Compare the rendering between Chrome 59 and Chrome 60. What is the expected behavior? The text should be legible, as in the 'Windows 7 Chrome 59.png' attachment. What went wrong? The text is illegible, as in the 'Windows 7 Chrome 60.png' attachment. Did this work before? Yes Chrome 59 Does this work in other browsers? Yes Chrome version: 60.0.3112.78 (Official Build) (64-bit) Channel: stable OS Version: 7 Flash Version: A workaround is to use SVG text with stroke and no fill.
,
Aug 9 2017
Sounds like a GPU issue, possibly related to r465279 Please attach the output from chrome://gpu Things to try: * open chrome://flags/#enable-gpu-rasterization and disable it * disable "Use hardware acceleration when available" in browser settings
,
Aug 9 2017
It occurs on the Browserstack Windows 7 and 10 instances. That's where I got the images from. It also occurs in the wild. I don't know a good way to grab the chrome://gpu output from Browserstack, but here's a screen grab of the top part of it.
,
Aug 9 2017
Disabling "Use hardware acceleration when available" in browser settings did not make any difference. Disabling chrome://flags/#enable-gpu-rasterization did not make any difference either.
,
Aug 9 2017
Looks fine for me in 60.0.3112.24 on Win 10. Win 7 only? Test team, please verify the bug and regression range.
,
Aug 9 2017
Stephen, can you test with --disable-gpu?
,
Aug 9 2017
How 'bout that. Reproduces in M-61 with software raster.
,
Aug 9 2017
Bisects to this Skia roll: https://chromium.googlesource.com/chromium/src/+/5412d363b9dec0df74ab2080665dc30cb3d9382f
,
Nov 28 2017
Reporter, is this still occurring? We have not had additional reports and this one continues to puzzle (tough to repro, bisects don't include obvious culprit)
,
Nov 28 2017
Yes, it still happens in the latest Chrome 62. You can view the test case on BrowserStack using a Windows 10 / Chrome 62 instance to see the problem. Happens in the 63 dev build there as well.
,
Aug 20
I can no longer reproduce this in Chrome 68 either locally or on BrowserStack.
,
Nov 21
Note: The tag on this bug is incorrect; it's supposed to be ReleaseBlock-* with no dash between the Release and Block. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by pdr@chromium.org
, Aug 9 2017