- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Apr 2018 14:29:58 +0000
- To: public-css-archive@w3.org
@frivoal The entire spec has a huge red "do not implement" notice, so I'm not sure the risk you're assessing is realistic. Nevertheless, I added an issue that links here to make it even more clear that the syntax is still under active discussion. I don't see a clear way forward with this, I think it needs to be discussed further. I agree with @tabatkins's concerns about usability (in fact, I raised them myself earlier in the thread). However, grouping with `stripes()` or a similar mechanism does not actually listify `border-color`. Listification typically extends the **current syntax** into multiples of the current syntax, and the current syntax accepts 1-4 space-separated values. Furthermore, aside from the grouping issue, it's insanely confusing that setting `border-color` can affect border width, and I'm not sure we'd make that resolution if we knew that. If we listified `border-width` too, we could make that one the property that determines the number of layers, and this issue wouldn't exist. In any case, more discussion is needed because this is not as simple as it seemed back when we resolved on it, and I think we need to bring it to the group again. @DavidMacDonald Not necessarily, you can always have transparent borders with the same properties when not focused, to avoid such jumps. However, any change we make to border will also be made to outline (per resolution), so you can use outline as well! -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1172#issuecomment-380120889 using your GitHub account
Received on Tuesday, 10 April 2018 14:30:03 UTC