Content disappears under translate3d, when beside an element with fixed
Reported by
jerem...@gmail.com,
Apr 4 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Example URL: Steps to reproduce the problem: 1. View the attached index.html/style.css in chrome on mac. (Note, this does not reproduce in jsfiddle, codepen etc. 2. Hold the mouse down on the button What is the expected behavior? The text in the button should slide right by 10px. What went wrong? The text in the button disappears. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 49.0.2623.110 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0 This works fine in Safari. NOTE. This is not reproducible in sites like jsfiddle and codepen. The code must be run independently in it's own Chrome window. The provided index.html/style.css is a very basic stripped down version of our web-app, with only the features of our web app necessary to reproduce. - The side panel - which represents a fixed menu - The animation/fade-in on load - The button moves down by 1px on click It looks like with this particular mix of elements with translate3d applied, Chrome thinks the text in the button no longer needs to be rendered - for example, if we make the side menu panel smaller the issue is gone. Leading me to think when the issue is there, it's like Chrome thinks the button text is under the panel when it's not.
,
Apr 4 2016
Able to reproduce the issue on mac 10.11 chrome version 49.0.2623.110 and canary - The text in the button disappears on holding the mouse on the button Issue can be seen in win and linux as well. This is working fine in Firefox and Safari - The text in the button slide right by 10px. This is a non regression issue existing since M43 43.0.2357.134 to latest canary M30 and before builds behavior : Button not clickable
,
Apr 4 2016
,
Feb 13 2017
,
Jun 7 2017
,
Sep 27 2017
This doesn't reproduce for me on ChromeOS HighDPI 60.0.3112.114 (Official Build) (64-bit) or Low DPI Linux Chrome 63.0.3223.8 (Official Build) dev (64-bit) or Linux Chrome 61.0.3163.100 (Official Build) (64-bit). Please re-open if the bug still reproduces but I suspect the underlying issue may have been resolved. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jerem...@gmail.com
, Apr 4 2016