SVG, flexbox and overflow: scroll cause rendering glitch on second screen
Reported by
iampetew...@gmail.com,
Jul 27
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.68 Safari/537.36 Steps to reproduce the problem: 1. Launch Chrome 2. Move window to second screen (mine is 1920 x 1080, non-retina) 3. Make sure window size is at least 450px high 4. Go to https://output.jsbin.com/mumijoquje 5. Scroll the right box down to the bottom What is the expected behavior? Page should repaint as normal What went wrong? The top portion of the page repaints at double scale (see video) Did this work before? N/A Does this work in other browsers? Yes Chrome version: 68.0.3440.68 Channel: beta OS Version: OS X 10.13.6 Flash Version: This only seems to occur when there is more than one column on the page, and when there is at least one SVG in the right column. I'm running macOS High Sierra 10.13.6 on a Macbook Pro 15" 2012 (with retina) My second screen is a Samsung SMB2430H Display, running at 1920 x 1080 The rendering glitch doesn't occur if the page is rendered in an iframe - e.g. https://jsfiddle.net/kjt1p5r8/show
,
Jul 30
,
Jul 30
I've recreated the jsbin @ https://output.jsbin.com/maxobus/1 - the previous one expired as it was created with an anonymous account. Note that the bug doesn't trigger on the embedded version @ https://jsbin.com/maxobus/1/edit?html,output
,
Jul 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 30
Additionally, I've now also seen this on a different display. This one's a creaky old CIBOX LW1922C @ 1440 x 900 resolution connected via a VGA adapter. Also non-retina.
,
Jul 31
Unable to reproduce the issue on reported version #68.0.3440.68 using MacBook Pro (Retina, 15inch,Mid 2015) 10.13.3 and second screen is Hp Desktop, running at 1920 x 1080(non-retina), by following below steps Steps: ===== 1.Launched chrome 2.Moved the window to second screen 3.Resized window to ~450px X 671px 4.Opened the test-case.html and https://output.jsbin.com/maxobus/1 5.Scrolled down the right side of window - could observe the page repaint is normal. Attached is the screencast for reference. @reporter : Could you please try to test this issue by creating new profile with no apps and extensions in it and let us know if the issue still persists and requesting you to test the issue on latest stable #68.0.3440.75, you can download the latest stable from : https://www.chromium.org/getting-involved/dev-channel Thanks!
,
Aug 1
Oh, man! I was afraid I'd be the only one seeing this... I've upgraded to #68.0.3440.75, and loaded a new profile with no extensions - can confirm it's still an issue for me. Please see attached screencast.
,
Aug 1
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 1
As a side-note, I'm also seeing this in the Canary channel - #70.0.3508.0
,
Aug 2
Unable to reproduce the issue on #68.0.3440.75 on using MacBook Pro (Retina, 15inch,Mid 2015) 10.13.3 and second screen is Hp Desktop, running at 1920 x 1080(non-retina), by followed the steps as per comment#0. Hence removing Needs-Bisect label as it is not getting reproduced from TE end.Requesting anyone from Blink>Paint team to look into the issue. Thanks.!
,
Aug 13
The NextAction date has arrived: 2018-08-13
,
Aug 13
As per comment #6 and #10, as this issue is not reproducible at TE end, adding 'TE-NeedsTriageHelp' and requesting the appropriate team to look into this issue and help further. Thanks..
,
Aug 13
I have to assume it's a device scale factor issue. I'll try to find someone who can try to reproduce.
,
Aug 27
ccameron@, do you have a setup that might reproduce this? Assign back if not.
,
Aug 27
Yes, I can try to reproduce it tomorrow.
,
Sep 4
Not sure if a change has been made, but this no longer affects me in #69.0.3497.72
,
Sep 4
Thanks for reporting it fixed in M-69. At this point I think we will not take any further action. Please re-open if the problem recurs. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by schenney@chromium.org
, Jul 29NextAction: 2018-08-13