- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jan 2022 17:29:30 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-values-4] Allow an inline way to do "first value that's supported"`, and agreed to the following: * ``RESOLVED: add `first-valid` and please add an issue to bikeshed the name once we better understnad the scope`` * ``RESOLVED: add `first-valid` and please add an issue to bikeshed the name once we better understand the scope`` <details><summary>The full IRC log of that discussion</summary> <emeyer> Topic: [css-values-4] Allow an inline way to do "first value that's supported"<br> <emeyer> github: https://github.com/w3c/csswg-drafts/issues/5055<br> <emeyer> TabAtkins: This is trying to address an issue that’s become more prevelant as variables have become more common.<br> <argyle> right at the good part!<br> <emeyer> …CSS lets you use new features and fall back to old ones by writing something twice.<br> <emeyer> …Variables break this. We assume things are valid at parse time, and only find out later whether or not they are.<br> <emeyer> …This same problem is going to come up with more things that do things at parse time.<br> <lea> q?<br> <lea> q+<br> <emeyer> …Proposal is to allow things to sub in the first thing the UA understands at parse time.<br> <dbaron> ... has to be the full value of the property<br> <emeyer> …This will need some clarification about how it can or can’t be nested. So we’ll want to define some contextual stuff.<br> <emeyer> …Overall it’s an attempt to get parse-time fallback behavior.<br> <fremy> huge +1 of course<br> <astearns> ack lea<br> <emeyer> lea: This would be incredibly useful. Would it be availabnle in descriptors as well?<br> <emeyer> TabAtkins: I don’t see why not.<br> <emeyer> s/availabnle/available/<br> <emeyer> florian: So this is no different than writing a thing twice?<br> <emeyer> TabAtkins: Correct.<br> <emeyer> emilio: This would go away at parse time?<br> <florian> s/So this is no different than writing a thing twice?/So this is no different than writing a thing twice if you use it without variables?<br> <emeyer> TabAtkins: Correct.<br> <emeyer> emilio: That seems fine.<br> <emeyer> astearns: Any concerns?<br> <emeyer> …So the resolution is to add `first-of` to Values. Any objections?<br> <emeyer> florian: Just wondering about the name of it. If people see this out of context, will they think it’s a list manipulation thing?<br> <lea> Yeah, as much as I like terse names, first-of() is confusing<br> <lea> q?<br> <lea> q+<br> <emeyer> TabAtkins: It’s possible there will be misinterpretation, but at least they’ll run into confusion quickly.<br> <lea> q-<br> <miriam> +1 first-valid<br> <smfr> +1 on first-valid<br> <emeyer> florian: How abotu `first-valid`?<br> <emeyer> s/abotu/about/<br> <emeyer> TabAtkins: I like it.<br> <fremy> @emeyer: that was me<br> <emeyer> fremy: I support that.<br> <emeyer> astearns: We can bikeshed the name later. Any objections to the idea?<br> <emeyer> …We are resolved to add `first-valid` and please add an issue to bikeshed the name once we better understnad the scope.<br> <astearns> RESOLVED: add `first-valid` and please add an issue to bikeshed the name once we better understnad the scope<br> <emeyer> RESOLVED: add `first-valid` and please add an issue to bikeshed the name once we better understand the scope<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5055#issuecomment-1022425917 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 January 2022 17:29:32 UTC