Issue metadata
Sign in to add a comment
|
CSS Typed OM: getComputedStyleMap returns the resolved value instead of the computed value
Reported by
martin.a...@gmail.com,
Nov 9 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 OPR/41.0.2353.46 Steps to reproduce the problem: 1. Enable the experimental-web-platform-features flag 2. Create a div element with the styles width: auto; height: 100%; 3. Call getComputedStyleMap for that element 4. Look at the width and height properties of the map What is the expected behavior? The computed values `auto` and `100%` should be shown in the console What went wrong? The resolved values `1920px` and `0px` are shown instead Did this work before? N/A Does this work in other browsers? N/A Chrome version: 56.0.2911.0 Channel: canary OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0 Related bug: 545318 The spec <https://www.w3.org/TR/2016/WD-css-typed-om-1-20160607/#dom-window-getcomputedstylemap> states: > The StylePropertyMap returned by getComputedStyleMap represents computed style, > not resolved style. In this regard it provides different values than those in objects > returned by getComputedStyle.
,
Feb 13 2017
,
Feb 13 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dstockwell@chromium.org
, Nov 9 2016Status: Available (was: Unconfirmed)