Issue metadata
Sign in to add a comment
|
clip-path and child element position
Reported by
nicola.d...@octoplus.ch,
May 8 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. open axure-broker.ch 2a. pay attention to white logo text 2b. open menu and pay attention to white menu labels What is the expected behavior? childs elements (white texts in point 2a and 2b) are inside a container with clip-path (animated with anime.js) and their position doesn't have to move from origin What went wrong? the origin position move following clip-path origin shape Did this work before? Yes v65 Does this work in other browsers? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
May 8 2018
,
May 9 2018
Thanks for filing the issue! Tried checking the issue on reported chrome version 66.0.3359.139 using Mac 10.13.1 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://axure-broker.ch Observed the text "Axure" changed its position(Up/down) while red background changes to white. Attaching the screen cast of the same. @Reporter: As we are not very sure about the issue, Could you please have a look at the screen cast and confirm it, your confirmation helps us to triage the issue further in a better way. Any further inputs from your end may be helpful.
,
May 9 2018
Hi Vamshi, thank you for your reply. I confirm the cast. During loading part you can see white text move from up to down. That's is the problem. The aspected behavior is that the white text is fixed on center of the page. You can find same issue if you try to open menu where white text is moving from up to down. There are other section where this problem is affecting. Loading part and menu are two example. My hypothesis is that content positioning of child element following clip path shape of parent container. The aspected behavior is that the content remain fixed and NOT following the clip-path shape. You can check the aspected behavior on chrome v65 (tested on browserstack and in native chrome before the update from v65 to v66). You can also check the aspected behavior on chrome v68 Canary. Find in attachment the screen cast from chrome v68 Canary of the aspected behavior Thank you
,
May 9 2018
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
,
May 10 2018
Triaged the issue further as per the confirmation given in comment#4 by reporter. Able to reproduce the issue on reported chrome version 66.0.3359.139 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is not seen(i.e., got fixed) in latest canary 68.0.3425.0, hence providing reverse bisect info. Bisect information: =================== Last Bad Build : 67.0.3396.0 First Good Build: 68.0.3397.0 You are probably looking for a change made after 550842 (known good), but no later than 550843 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/05ddc86fb4db1a2b8dc9c4faa02d61b99218db2f..10a4e34cc9207c2f6045ae5154cded6fed51f995 Suspecting: https://chromium.googlesource.com/chromium/src/+/10a4e34cc9207c2f6045ae5154cded6fed51f995 Review URL: https://chromium-review.googlesource.com/1006395 Note: Adding RB-Stable as this seems to be a recent regression, Please remove if not required. @Tien-Ren Chen: Please help in re-assigning it to the right owner if this is not related to your change. Thanks!
,
May 10 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, May 8 2018