- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 May 2018 18:19:24 +0000
- To: public-css-archive@w3.org
While that's a reasonable concern, it's much less important for forward-compat than the one I gave. "Don't serialize shorthands at all" means you'll *automatically* break code that depends on the serialization of that property as soon as you ship the change turning a longhand into a shorthand. "Serialize shorthands" breaks *zero* code when you ship the new feature; it only breaks stuff if the page is further updated to take advantage of the new, unserializable, feature. At that point the maintainer can just fix that code as well (or otherwise work around it), since they're already there altering the page. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2529#issuecomment-386389645 using your GitHub account
Received on Thursday, 3 May 2018 18:19:25 UTC