W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2017

[csswg-drafts] [cssom] Doubt about resolved value of shorthands

From: Manuel Rego Casasnovas via GitHub <sysbot+gh@w3.org>
Date: Thu, 16 Feb 2017 09:29:04 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-208065880-1487237342-sysbot+gh@w3.org>
mrego has just created a new issue for 

== [cssom] Doubt about resolved value of shorthands ==
Spec text: https://drafts.csswg.org/cssom/#resolved-value
> The resolved value for a given longhand property can be determined 
as follows:
> * A bunch of properties defining it.
> * A resolved value special case property defined in another 
>   As defined in the relevant specification.
> * Any other property.
>   The resolved value is the computed value.

The spec talks about **longhand** so I'm not sure what's the expected 
behavior for shorthands.

I've tried the following example for the [`flex` 
  <div style="display: flexbox;">
    <div id="flexitem" style="flex: 1;">item</div>
    console.log("flex: " + 

The output in Chrome, Safari and Edge is:
  flex: 1 1 0%

However in Firefox it's:

In a [different 
 @upsuper commented:
> IIRC in general we don't serialize new shorthands in computed style,
 only longhands are serialized there. There are several shorthands get
 serialized in computed style just for backward compatibility.

What's the expected behavior?
Should the spec be updated to be clearer about the resolved value of 

Thanks! :smile: 

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/1041 using your GitHub 
Received on Thursday, 16 February 2017 09:29:10 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:08 UTC