- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jan 2022 18:05:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Make box-shadow a shorthand`. <details><summary>The full IRC log of that discussion</summary> <emilio> topic: Make box-shadow a shorthand<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/4431<br> <emilio> TabAtkins: we've discussed about this in the past<br> <emilio> ... people want to animate one bit of a shadow, like increasing the spread etc<br> <lea> +q to express support<br> <emilio> ... you can always use custom props and so on and it seems so straight-forward that I think we could try<br> <TabAtkins> https://github.com/w3c/csswg-drafts/issues/4431#issuecomment-790113613<br> <emilio> ... sebastian proposed a grammar (link above)<br> <smfr> q+<br> <emilio> TabAtkins: (describes linked proposal)<br> <emilio> lea: I want to express support, this is a very common thing. It's one of the first examples I use for custom props<br> <emilio> ... is there an inset prop?<br> <emilio> TabAtkins: yeah<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/4431#issuecomment-790113613<br> <emilio> lea: can we do it for text-shadow too?<br> <Rossen_> ack lea<br> <Zakim> lea, you wanted to express support<br> <emilio> TabAtkins: yeah, also in the proposal<br> <Rossen_> ack dbaron<br> <emilio> dbaron: I guess one of my reactions is that the stuff that background does is one of the most complicated parts of implementing value computations on CSS<br> <emilio> ... the code for dealing with that was a significant part of the old parser<br> <emilio> TabAtkins: for this there is one controlling property<br> <emilio> dbaron: true for backgrounds as well (for background-image)<br> <emilio> ... and you need to keep the whole list because you might inherit it somewhere where it matters<br> <Rossen_> q?<br> <emilio> TabAtkins: isn't this a common pattern like animation?<br> <emilio> dbaron: yeah, but it's special code every time<br> <emilio> smfr: should box-shadow-offset be further broken down into x/y offsets?<br> <emilio> TabAtkins: [meh reaction]<br> <emilio> q+<br> <emilio> ack smfr<br> <emilio> ack fantasai<br> <Zakim> fantasai, you wanted to mention that -position needs renaming 'cuz it's not a <position><br> <Rossen_> ack fantasai<br> <Rossen_> ack emilio<br> <fantasai> emilio: Regarding what dbaron said, not just about parsing complexity but also efficiency<br> <fantasai> emilio: you need to store 5 different arrays rather than one<br> <delan> present-<br> <fantasai> emilio: so it's also a bit more inefficient<br> <lea> fantasai: box-shadow-offset perhaps?<br> <fantasai> emilio: maybe OK if we consider these to be relatively uncommon<br> <fantasai> emilio: The parsing complexity is real. Background is the worst by far, but need to check also transitions/animations. It's not super amazing<br> <fantasai> TabAtkins: Question is, is linked list-valued properties something we want to add generally, or not<br> <emilio> TabAtkins: the main q is whether adding more list-valued shorthands is ok, and if it's not we should not do it consistently<br> <emilio> dbaron: I wouldn't say never do them but it's more expensive than you might thing<br> <emilio> TabAtkins: curious, is the opinion different depending on "there's one length-controlling property vs. shortest wins"<br> <emilio> dbaron: I don't think it makes a huge difference<br> <emilio> ... only if you truncate computed values perhaps<br> <emilio> TabAtkins: that seems fine<br> <emilio> Rossen: let's follow-up in the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4431#issuecomment-1016728393 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 January 2022 18:05:20 UTC