Image not rendered correctly
Reported by
hubert@bigchilisoftware.com,
Sep 16
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Steps to reproduce the problem: 1. open this code pen https://codepen.io/hubertoehm/pen/RYYomq What is the expected behavior? all three div should look the same and the red background should not be visible. What went wrong? The image in the div in the middle is rendered incorrectly and shows the red background. Changing top from -2px to something else displays the image correctly. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3497.92 Channel: stable OS Version: 10.0 Flash Version: Actually the first and third div are also not rendered 100% right. The most left and right pixels of the image are blended with the red background, which should not happen, but is OK, nobody will notice that in real life. Microsoft Edge renders this test case perfectly though.
,
Sep 18
hubert@ Thanks for the issue. Able to reproduce the issue on Windows 10, Mac OS 10.13.3 and Ubuntu 17.10 on the latest Stable 69.0.3497.100 and the latest Canary 71.0.3555.0. On loading the given codepen, can observe a pixel with red background on the right and left of the div. Attached is the screen shot for reference. This is a Non-Regression issue as this is observed from M-60 chrome builds. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Sep 25
,
Sep 25
Only happens at certain zoom/dpi levels (125% most notably). The subtle red edges are likely due to subpixel layout, why the middle one gets wide bars at 125% though is interesting. Would you mind looking into this atotic? Broken in both legacy and NG.
,
Oct 3
Have a patch that fixes it, but makes 6 other tests look worse. Paint team is better qualified to decide what the right fix is. Take a look at test runs at: https://chromium-review.googlesource.com/c/chromium/src/+/1259832 The core of the problem is computing of container_size_without_zoom in SVGImageForContainer. Something like this happens: container_size = 392x55; zoomed_container_size = container_size * zoom; // 490x68.75 zoomed_container_size_int = PixelSnapped(zoomed_container_size) // 490x68 SVGImageForContainer(zoomed_rect_size_int, zoom); SVGImageForContainer(zoomed_rect_size_int ) { container_size_svg = zoomed_rect_size_int.Scale(1/zoom); // 392x54 // Error: container_size != container_size_svg } Also attaching a simple reproducible case.
,
Oct 3
Thank you Aleks! pdr, would you mind taking a look?
,
Oct 5
Another data point: - patch might be correct for legacy. Only 3 failures, and they all look correct, slightly different antialias. NG image list items fail differently. This actually might be an artifact of slight difference between NG and Legacy list image painting. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by susan.boorgula@chromium.org
, Sep 16