- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Sat, 04 Nov 2017 16:18:23 +0000
- To: public-css-archive@w3.org
> I'd also note that the normal rules for shorthands would produce a third result that is...undesirable
> [serializing the modern property as its "shorthand" alias]
This doesn't actually seem to be what Chromium does for the few properties where they (ab)use shorthands to do aliasing.
Sample ([live jsfiddle version](https://jsfiddle.net/rfr5vgd1/)):
````
document.body.style.webkitColumnBreakInside = "avoid";
console.log(document.body.getAttribute('style'));
````
This testcase produces `break-inside: avoid;` even though they implement `-webkit-column-break-inside` as a shorthand for `break-inside`, as shown [here in their source](https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/css/CSSProperties.json5?l=4467&rcl=8dfdd5c89b113097bbc34690f042cec6b4675363) and as noted in https://bugs.chromium.org/p/chromium/issues/detail?id=679068#c11
So, they do the Right Thing here, even though it's the opposite of normal shorthand behavior. (I wonder if that's due to a special-case codepath for shorthands that are only shorthands of a single property, maybe?)
--
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/866#issuecomment-341909418 using your GitHub account
Received on Saturday, 4 November 2017 16:18:25 UTC