SVGs not rendering correctly (related to hardware acceleration)
Reported by
corywat...@gmail.com,
Feb 22 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Example URL: http://heapanalytics.com/app Steps to reproduce the problem: This issue looks to be Mac only, related to hardware acceleration and is fixed when hardware acceleration is disabled. Unfortunately this app is behind a login, but here's a screenshot: http://cory.la/j99B Left side: Chrome non-retina Right side: Chrome retina Note the lack of detail in two icons: Visualizer and Funnel What is the expected behavior? Icons should be crisp. What went wrong? This broke in Chrome 56 and still appears broken in 57.0.2987.13 dev (64-bit). Only broken on OS X - Windows 10, Chrome 56 looks okay. Disabling hardware acceleration solves it. Worked fine in Chrome 55. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.13 dev Channel: stable OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 24.0 r0 Seems similar to this issue [1], but it appears that issue only happened on retina screens, whereas this issue happens only on non-retina. Also looked at this one [2] but that one seems to merged into 56 already, and didn't solve this particular issue. [1] https://productforums.google.com/forum/#!topic/chrome/fQ0TXZFg0I0 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=668550
,
Feb 23 2017
Is it possible to attach the screenshot(s) directly to this bug report?
,
Feb 23 2017
,
Feb 23 2017
Verified on Mac Chrome and Skia test app. Attaching image and skp of visualization icon.
,
Feb 23 2017
The SDF path renderer just doesn't have the resolution to represent the fine detail in these icons. We'll need another method for them.
,
Feb 23 2017
The short-term solution is to stop using distance fields on desktop unless we're scaling up (in which case we can save space in the atlas). This is less of a problem on Android because of higher screen resolutions (i.e., we're already scaling up). Long-term, we can use other path rendering methods or the new SDF generation algorithm, which seems to provide sharper results (but still has many bugs).
,
Feb 24 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Feb 23 2017