svg clipPath doesn't render when inspecting via adb
Reported by
ciriousj...@gmail.com,
Sep 3
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Download html file 2. Open on mobile 3. Connect via chrome://inspect What is the expected behavior? The screenshot should look identical What went wrong? The clippath renders correctly on the phone, while it doesn't show at all in the dev tools. Did this work before? No Chrome version: 68.0.3440.106 Channel: n/a OS Version: 10.0 Flash Version: Notice that it won't bug out of the box, but it's the most I could narrow it down. If I remove either - will-change: transform; - position: absolute; - clip-path it won't work (eg. it doesn't bug anymore). However, as I said, in the index.html file it works properly, possibly because nothing has transformed. will-change can either have transform or opacity for the bug to occur. I assume, that some js initiated a transform, but I don't know which one. Sorry.. If you want the full sourcecode (non-public), I can provide it, but I don't think it speeds up anything.
,
Sep 3
Oh, sorry, I forgot to add the index.html Here it is:
,
Sep 4
,
Sep 4
Thanks for filing the issue! As per comment#0 steps to reproduce the problem, issue requires mobile device to test and confirm the issue, hence routing this to Inhouse team for further triaging and adding TE-NeedsTriageFromHYD label to it. Thanks!
,
Sep 6
T
,
Sep 6
Tested the issue on android and unable to reproduce the issue Steps to reproduce: -------------------------- 1. Launched chrome and opened attached .html file 2. Inspected and able to see image both in mobile and via chrome://inspect Chrome version: 69.0.3497.76 OS: Android 8.0 Android device: Pixel 2 @ciriousjoker: Please check the above steps and let us know if we miss anything. Is this issue consistently reproducible? Please let us know the device details along with chrome and android version you are using. Any information on reproducing the issue would help in better triaging. Thanks!
,
Sep 6
,
Sep 9
Yes, this issue is consistently reproducable, but I haven't found a minimum working sample yet without sending you guys the whole source code. I assume, that it has something to do with Material Web Components or Aurelia (aurelia-resize), because the original app is set up like this: <div resizeable resize.trigger="onContentResize($event)" style="clip-path: url(#clipPathBottomNavigation);"> <div class="mdc-tab-bar" role="tablist"> ... </div> </div>
,
Sep 9
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
,
Nov 2
I'll investigate and try to repro. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 Deleted