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

[csswg-drafts] [cssom] Serialization of CSS declaration block returned from getComputedStyle

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Tue, 14 Feb 2017 06:15:45 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-207427648-1487052944-sysbot+gh@w3.org>
upsuper has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [cssom] Serialization of CSS declaration block returned from 
getComputedStyle ==
How should CSS declaration block returned from `getComputedStyle` be 
serialized? It contains all longhand properties.

Currently, Gecko and Edge return empty string for it, while WebKit and
 Blink (probably inherit from WebKit) seem to return serialization of 
all longhand properties (i.e. not trying to generate shorthands). 
Apparently none follows the spec.

Following the same algorithm for `cssText` of declaration block from 
`getComputedStyle` is complicated, and probably isn't worth. So I 
suggest that the spec should either follow Gecko and Edge to return 
empty string, or follow WebKit and Blink to return all longhand 
properties.

I would prefer we just make it return empty string... But there is a 
webcompat issue reported to Firefox for lack of its support: 
webcompat/web-bugs#3822. This is a Google website though, so maybe we 
can just ask Google to fix it and ignore this issue...

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/1033 using your GitHub 
account
Received on Tuesday, 14 February 2017 06:16:05 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:29 UTC