Issue metadata
Sign in to add a comment
|
Rendering Bug When Animation Is Playing: Lines Appear Under Moving Element
Reported by
mobilesl...@gmail.com,
Jan 19 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version : 55.0.2883.95 OS Version: OS X 10.12.2 URLs (if applicable) : https://jsfiddle.net/7dnqour1/1/ Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: OK Firefox 4.x: IE 7/8/9: What steps will reproduce the problem? 1. Follow the JSFiddle linked above 2. Green lines appear under the moving element What is the expected result? No green lines appear behind the moving object. What happens instead of that? Green lines (rendering artifacts?) appear behind the moving element. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
,
Jan 20 2017
,
Jan 20 2017
Unable to reproduce the issue on mac 10.12.2 chrome version 55.0.2883.95 and canary 57.0.2986.0 - No green lines appear behind the moving object Please find the screencast Could you please try the same on a new profile and see if issue still exists. You can create anew profile from chrome://settings
,
Jan 24 2017
,
Jan 25 2017
I can't reproduce on 55.0.2883.95 or any other version on Mac w/retina and w/ and w/o --prefer-compositing-to-lcd-text
,
Jan 25 2017
Same for GPU raster. Bug reporter: can you reproduce on Chrome 56 beta?
,
Jan 25 2017
@chrishtr yes, I can reproduce on Chrome 56 beta (specifically: Version 56.0.2924.67 beta (64-bit)) I also grabbed a copy of Canary, and can reproduce there too (Version 58.0.2991.0 canary (64-bit)) This is all on the same Retina MacBook Pro w/ TouchBar (2016).
,
Jan 25 2017
Very strange. Could you post the output of chrome://gpu/ ?
,
Jan 25 2017
,
Jan 27 2017
Could test please try to reproduce on a new Mac with Touchbar?
,
Jan 30 2017
,
Jan 30 2017
,
Feb 10 2017
I am able to reproduce this issue on Latest Stable#56.0.2924.87, Beta#57.0.2987.37 & Dev#58.0.3004.3 for Mac OS X 10.12.3 (Touch Bar), however it is working as intended on Latest Canary#58.0.3007.0. Here is the change log: https://chromium.googlesource.com/chromium/src/+log/58.0.3004.0..58.0.3007.0?pretty=fuller&n=10000 wangxianzhu@, could you please confirm this change (https://chromium.googlesource.com/chromium/src/+/94d07a45f859a3430ea9de1ff8c2a95708cb23b1) has caused the above fix? If so can you please merge this to other channels? Thank you!
,
Feb 10 2017
,
Feb 10 2017
https://chromium.googlesource.com/chromium/src/+/94d07a45f859a3430ea9de1ff8c2a95708cb23b1 doesn't look like the fix. manoranjanr@ can you bisect with revisions to get a smaller range using the following command? Thanks. bisect-builds.py -a mac64 -g 449173 -b 448183 -- https://jsfiddle.net/7dnqour1/1/
,
Feb 13 2017
@MTV Team -- Could someone from MTV team look into this as inhouse-HYD-team doesn't have touch Mac Machine. Thanks!
,
Feb 13 2017
Sorry, please ignore the above CL (c#13). Good#58.0.3004.0 Bad#57.0.2987.0 Here is the narrowed bisect: https://chromium.googlesource.com/chromium/src/+log/d297fb597145bbfc86fb1c243091669f09dc6df5..f611080eb86df037b4e687dc9d2821d68721d724 Suspecting https://chromium.googlesource.com/chromium/src/+/9686be68e53348bab6f4ce846bf07d494f1575a0 ? Thank you!
,
Feb 15 2017
Currently we don't have plan to enable SlimmingPaintInvalidation on m57. Move the bug to m58 because this is not marked a regression. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by karandeepb@chromium.org
, Jan 20 2017