CSS 3D transform basic rotation causes erroneous intersection of DOM surfaces, and glitches
Reported by
trusktr@gmail.com,
Jan 21
(2 days ago)
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Open the HTML file included in the zip file 2. Note that at first some of the DOM surfaces are not intersecting with the background. 3. Interact with it (try selecting text, hover in the Chrome tabs and plugin icons, etc) 4. Notice that intersection can switch to being correct when you scroll the containers, or when you highlight text, etc. 5. Also notice that when hovering in Chrome's chrome, it glitches out the rendering. The above is depicted in the included GIF and MP4 files inside the ZIP file. It works fine in Firefox and Safari. What is the expected behavior? There should be no glitches, intersections should be fine. What went wrong? The planes (elements) don't always intersect with the background. Notice that the element at the top left of the container always seems to intersect correctly, while other ones don't. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 71.0.3578.98 Channel: stable OS Version: OS X 10.14.2 Flash Version: It'd be great for this to be fixed. CSS transforms have been buggy and ugly in Chrome for quite a while now: - https://bugs.chromium.org/p/chromium/issues/detail?id=799823 - https://bugs.chromium.org/p/chromium/issues/detail?id=709510 I would really dislike to ship experiences with these sorts of glitches to end users. Is CSS 3D not being tested well? The impression I get is that CSS 3D is not receiving any more love in Chrome.
,
Yesterday
(43 hours ago)
Tested the issue on chrome reported version# 71.0.3578.98 using Mac 10.12.6 with steps mentioned below: 1) Launched chrome reported version, dragged and dropped '.html' file provided in comment# 0 2) Hovered the mouse at omnibar area, observed glitches at element at top right of container Observations: Tested the issue on chrome version# 73.0.3678.0, observed the glictches at top right element, please find the attached screencast of chrome version# 60.0.3112.0, but didn't observed nay glitches there. @Reporter: Please find the attached screencast for your reference, let us know if the behaviour captured in the screencast is the excepted behaviour, provide your feedback o it which help in further triaging the issue in better way. Thanks!
,
Yesterday
(24 hours ago)
Hello Viswa, looks like some of the glitches are there in your screencast. Although hovering on the omnibar area in your screencast didn't cause the rendered image to change like in my examples, you can still notice that the elements will pop out from behind the background as you move the mouse around. In particular, notice that the top-right element does not intersect with the background. Also notice in some parts of your screencast that the bottom elements don't fully intersect. In the attached screenshot of your screencast, on the bottom of the elements is visible a small slice, which is a portion of the element that should be occluded behind the background, but is instead visible. The missing portion that you see in my video, where the top-right element is missing a portion, seems to be a similar effect as the missing portions visible in your screencast of the bottom elements, but in your case not triggered while hovering on the omni bar. Hope that makes sense! I've also attached another video showing some more glitches, but I'm not sure if they're related, and I don't have a simple reproduction of those ones yet.
,
Yesterday
(24 hours ago)
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 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Jan 21 (2 days ago)