Element with position:fixed is not correctly positioned when an ancestor has a filter applied
Reported by
javier.c...@gmail.com,
Jul 26
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36 Steps to reproduce the problem: 1. Open the attached file 2. See how the text has the margin from the `body` applied 3. Remove `filter: grayscale(100%);` from the parent with class `container 4. See how the text div is correctly placed What is the expected behavior? The text div should be placed in the top left corner, without the body margin being applied to it What went wrong? It seems using `filter` in the ancestor of an element with `position: fixed` somehow breaks the positioning of that children. Did this work before? Yes 67 Does this work in other browsers? N/A Chrome version: 68.0.3440.75 Channel: stable OS Version: OS X 10.13.6 Flash Version:
,
Jul 27
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 68.0.3440.75 and on the latest canary 70.0.3504.0 using Mac 10.13.1, Ubuntu 14.04 and Windows 10. Bisect Information: ------------------- Good Build: 68.0.3423.0 Bad Build: 68.0.3424.0 You are probably looking for a change made after 556633 (known good), but no later than 556634 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/1c5817775b404d9f128fffe8911ffa6d109c881b..ecde43d3de87b7ad6b15be5677ad5f0ac53aad2c Suspecting: https://chromium.googlesource.com/chromium/src/+/ecde43d3de87b7ad6b15be5677ad5f0ac53aad2c Review URL: https://chromium-review.googlesource.com/1045624 @Chris Harrelson: Please help in assigning it to the right owner if this is not related to your change. Note: Adding RB-stable as this seems to be a recent regression.
,
Jul 27
This is an intentional change. Filter is now a containing block for all descendants, including fixed-position. See: https://www.chromestatus.com/features/5666287510355968 https://drafts.fxtf.org/filter-effects-1/#FilterProperty Firefox has the same behavior already. The Chrome behavior is a change in version 68. |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Jul 26