W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2018

[csswg-drafts] [cssom] getComputedStyle and shorthands.

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Apr 2018 10:05:16 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-313256561-1523441114-sysbot+gh@w3.org>
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:

== [cssom] getComputedStyle and shorthands. ==
Currently https://drafts.csswg.org/cssom/#dom-window-getcomputedstyle says:

> declarations: All longhand properties that are supported CSS properties, in lexicographical order, with the value being the resolved value computed for obj using the style rules associated with doc.

Which means that `getComputedStyle(document.documentElement).font` shouldn't be present, since it's a shorthand.

This is inconsistent with https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-getpropertyvalue, though which handles shorthands.

Should `ComputedStyle.getPropertyValue` handle shorthands? If so, should they be exposed as a property in the declaration object?

Right now answers from browsers to "does `getPropertyValue` handle shorthands?", and "are shorthands exposed as a property?" are:

 * Firefox: no, no
 * WebKit / Blink: yes, yes
 * Edge: no, no

What should happen here?

Note that both FF and Edge have a special-case for `overflow`, which used to be a longhand.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2529 using your GitHub account
Received on Wednesday, 11 April 2018 10:05:27 UTC

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