-webkit-box-reflect + filter: drop-shadow = incorrect replica layer offset |
||||
Issue descriptionWhile exploring -webkit-box-reflect: discovered this weird quirk: http://jsbin.com/livobi/2/edit?html,css,output The reflection shouldn't move because the shadow blur radius changes. It should be aligned with the source rectangle. Pri=3 because this is unlikely to actually be a common case on the web, but filing so that we have it on record.
,
Mar 8 2016
It does move for me, but the reflected box slides along a line of slope 1 for some reason. And yeah, the non-composited path is broken in yet more silly ways.
,
Mar 9 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 9 2017
Seems fine in r454471. According to bisect-builds, this was fixed by something in this range: https://chromium.googlesource.com/chromium/src/+log/fb6d7cd97f963253a64b8234954d0f76fa310871..25d2a4a86fb664bbeff65fb68f835c92cd6318c4 Most likely by "Accelerated filters should filter unpadded primitives" (r370523), where we stopped padding textures with transparent pixels before passing them to Skia.
,
Apr 5 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by pdr@chromium.org
, Mar 8 2016