- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Jan 2019 13:44:41 +0000
- To: public-css-archive@w3.org
@fantasai Mostly it's just that the priority was to ship the same logical properties as Firefox, so I didn't include the shorthands in the intent to ship. It may make sense to send another one about the shorthands, especially since [Firefox plans to start shipping them](https://groups.google.com/forum/#!topic/mozilla.dev.platform/gpubhXTxI6o). My only concern is that things like #1282 have not been decided yet, and may require changes that will be observable via CSSOM (e.g. `margin` becoming a shorthand for both physical and logical longhands instead of just the physical ones). Adding shorthands may increase the number of properties with breaking changes. Also, some shorthands may be safer than others, e.g. there was a [complaint](https://crbug.com/876913) about `top:0;bottom:0;left:0;right:0` becoming `inset:0px` in `cssText`. The main problem was that this happened despite `inset` being disabled behind a flag, but I hope people are not relying on a serialization with longhands. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3486#issuecomment-454396476 using your GitHub account
Received on Tuesday, 15 January 2019 13:44:42 UTC