- From: Nicolás J. Engler via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Dec 2017 12:18:57 +0000
- To: public-css-archive@w3.org
> Our stated reason was that the aspect-ratio hack was the only significant case (that is, the only case that showed up in non-trivial numbers in our use-counters) for using % padding in the first place. Virtually nobody was using % padding for anything else at all.
>
> Thus, there was no argument for making %s relative to each axis, besides a weak sense of theoretical purity ("what it should have been to start with"). And, since we can't change the behavior for block layout, that's directly clashing with the other theoretical-purity argument, that %s on padding should work the same in all display modes.
I'll have to agree with @tabatkins here, there's been previous cases where the spec leans on an already established behavior or convention rather than theoretical purity, and a reduced example case could be the spelling of the `nowrap` value for the `white-space` property. Maintaining consistency and following Chrome's approach seems more logical to me, however I'd still like to see an expansion of @marcvangend's idea for `%w` or `%h` units, independently of their spelling (I'm up for using syntax similar to those of viewport-relative units), as it provides a more granular control.
--
GitHub Notification of comment by NicolasJEngler
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2085#issuecomment-354105964 using your GitHub account
Received on Wednesday, 27 December 2017 12:19:00 UTC