Z-Translated Elements Ignore Clip Path
Reported by
alex.li...@celtra.com,
Dec 15 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Example URL: https://jsfiddle.net/pzsLm42z/ Steps to reproduce the problem: 1. Create a div with a clip-path. 2. Add a single child div with a Z-Translation of any length, including 0. What is the expected behavior? The parent div should clip the child div: https://jsfiddle.net/jz943Lsb/ What went wrong? The child div is completely visible as if no clip-path was specified. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: Debian stretch/sid Flash Version: Shockwave Flash 24.0 r0 Regardless of its values, using a translate3d transform will always cause this problem. Using a translate (2D) transform will not: https://jsfiddle.net/zzpj5p33/ Z-Rotated elements appear to behave normally: https://jsfiddle.net/2jn0nm3e/ We don't believe this is exclusive to a particular clip-path type: https://jsfiddle.net/5znm9e47/
,
Dec 16 2016
,
Dec 16 2016
,
Dec 16 2016
able to reproduce the issue on Mac 10.12, Win 10 and Ubuntu 14.04 using stable 55.0.2883.87/95 and previous stable 54.0.2840.89/99. This is fixed in the latest canary 57.0.2952.0 and is working as intended. Reverse bisect: ============= Good:57.0.2947.0 Bad :57.0.2946.0 You are probably looking for a change made after 437634 (known good), but no later than 437635 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/9b853cfcf82d8c57487cb0dd8d1eeaa5ca40260f..3de2a45741756dfa0640ce1037a76ee9eedabfbb Fixed at : Review-Url: https://codereview.chromium.org/2558633005 smcgruer@ : Could you please check this issue if its related to your change. The issue seems to be similar to Issue 615870 .
,
Dec 16 2016
Adding Releaseblock-stable and requesting to merge into M55 and M56, please modify if not appropriate.
,
Dec 16 2016
This is not a regression (as #4 points out in the comment text). It is a dupe of Issue 615870 which is a long standing bug since at least M51 (likely earlier). As this is not a regression, I see no reason to merge to M55 or M56. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tkent@chromium.org
, Dec 15 2016