'getComputedStyle' returns different value in chrome 50 and 51
Reported by
manimara...@gmail.com,
Jun 6 2016
|
|||||
Issue descriptionChrome Version : 51.0.2704.79 m URLs (if applicable) :https://jsfiddle.net/p3qw3u5L/7/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: IE: Chrome : 50.0.2661.102 - OK What steps will reproduce the problem? (1)create element with position as 'absolute' (2)Calculate the element's value for top and bottom using 'getComputedStyle' api What is the expected result? It should return the value as 'auto' What happens instead? It's returning the value (e.g: '70px') Please provide any additional information below. Attach a screenshot if possible.
,
Jun 7 2016
Able to reproduce this on the latest canary(53.0.2761.2) and the latest stable(51.0.2704.84) on Windows-7, Mac OS 10.11.5 and Linux Ubuntu 14.04. This is a regression issue broken in M-51. Last good build: 51.0.2701.0 First bad build: 51.0.2702.0 Changelog:https://chromium.googlesource.com/chromium/src/+log/51.0.2701.0..51.0.2702.0?pretty=fuller&n=10000 On manual inspection this looks to be caused by https://codereview.chromium.org/1826423003 Kevin@: Could you please take a look at this. Marking this as RB-Stable for next stable refresh if there is one.
,
Jun 7 2016
,
Jun 7 2016
Till now, we trusted chrome. But from last 5-6 releases, Chrome is getting unstable and losing the developers trust.. We are logging issues for every stable release. Can you please release a fix for the latest stable channel - minor update?
,
Jun 7 2016
See issue 589347 , this is not a regression.
,
Jun 9 2016
As per comment 5, this is working as intended. My understanding is that the behavior change means Chrome now matches the behaviour in the specifications as well as Firefox. I'm going to leave this bug open for now so it's easier to search for, but as the change increases compatibility with FF and the specs I don't expect that we'd revert to the old behaviour.
,
Jun 15 2016
,
Jun 15 2016
I guess the workaround is to set the element's display property to none, call getComputedStyle, which will now return auto where expected, then unset the display property again.
,
Jul 8 2016
Just a note to confirm that this is working as intended.
,
Aug 15 2016
Working as intended |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nssmanik...@gmail.com
, Jun 6 2016