- From: Daniel Tonon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Jul 2018 22:12:40 +0000
- To: public-css-archive@w3.org
@AmeliaBR > Unless the plan is to extend this property to apply beyond first child or first pseudo-element in a block, I think it is useful to preserve the initial- (or initials-) prefix for the properties. What's to say that this isn't a possibility in the future? Remember how we started off with `grid-gap` but then everyone said that they wanted `grid-gap` in flexbox? The name `grid-gap` didn't make sense in flexbox though so it was changed to just `gap`. That was a mess that we would have preferred to avoid. Naming a property based on what restrictions the _current_ spec has on it isn't future proofing the property. If we want to extend this functionality to floated images (something I can definitely see happening one day) we want a more generic property that will still make sense in that context. That being said I **LOVE** the idea of `line-span` as the new name. - It does exactly what you think it does - we already have the `line` term in `line-height` and "line" means the same thing in both of them so I don't think it is going to get confused for anything - `span` is the perfect term for how it behaves since it aligns with how we think of `span` in CSS Grid - it is abstract enough to be used on anything if the spec changes in the future to alow it to be used in more contexts - you don't need any graphic design hystory knowledge to understand the naming of the term - it is easily translated into other languages I definitely 100% vote for `line-span` as the new property name. ❤ -- GitHub Notification of comment by Dan503 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2950#issuecomment-407913457 using your GitHub account
Received on Wednesday, 25 July 2018 22:12:44 UTC