New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 663861 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 648495
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Blocking:
issue 545318



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 description

UserAgent: 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.
 
test.html
283 bytes View Download
Blocking: 545318
Status: Available (was: Unconfirmed)
Labels: Update-Monthly
Owner: rjwright@chromium.org

Comment 3 by meade@chromium.org, Feb 13 2017

Mergedinto: 648495
Status: Duplicate (was: Available)
Renee is currently working on this.

Sign in to add a comment