Computed bottom property is not correct when position is relative
Reported by
stefan.neculai@gmail.com,
Apr 25 2016
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36 Steps to reproduce the problem: 1. Go to https://jsfiddle.net/fvn9cz1s/. 2. You will see an alert with the bottom property. What is the expected behavior? Bottom should be 'auto', not '0px'. What went wrong? Computed bottom property is not correct. Did this work before? Yes Chrom 50.0.2661.86 (64-bit) works just fine Chrome version: 52.0.2715.0 canary (64-bit) Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0 Got a report that same thing is happening in Chrome 51.0.2704.22 beta-m (64-bit).
,
Apr 26 2016
This returns auto for me both on stable, beta and dev.
,
Apr 26 2016
Here is a recording of the issue. Maybe that is happening only on OS X?
,
Jun 14 2016
Could you please review this again? It is happening starting with version 51.0.2704 in Chrome browser it was not happening before. It appears that CSS property position: relative is causing this problem. See https://jsfiddle.net/t7r62gg8/. Safari browser is returning auto, auto in both cases. Thank you in advanced for considering this.
,
Jun 14 2016
We have this problem too. Will this be reopened or should we create a new Issue?
,
Jun 14 2016
,
Jun 15 2016
I can confirm that I get the unexpected result of 0px, using both Chrome on Windows 10 and OS X. Here are my user agents: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36
,
Jun 22 2016
,
Jun 23 2016
bisect result: https://chromium.googlesource.com/chromium/src/+log/bc3ebdc42cd0b29fd770213d02a99a81b84dc69c..d53da75cc2009064b8ce54c734b7eb6f8387c031 most likely https://chromium.googlesource.com/chromium/src/+/f3b023bb8511c3734d1207e9cf78c61f67826af0%5E%21/ It's reproducible on linux64.
,
Jun 23 2016
It's intentional, please see http://crbug.com/589347 . The change was introduced for better compatibility with Firefox which returns 0px for the provided example. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by dtapu...@chromium.org
, Apr 25 2016