- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 May 2024 19:03:30 +0000
- To: public-css-archive@w3.org
Recall that the discussion in the joint meeting was that we could always add `base` later, after we'd gotten all the current controls figured out, and just define that it behaves as the appropriate value depending on the element (or `none` or `auto`, if there's no more specific value). That way we get: * the forward-compatibility benefits immediately, without delaying *at all* * an established structure for other variants, like what Anne mentioned for a select-without-picker mode * an easy way to verify that a given element's base styling exists (by doing a supports query for the specific value) This isn't new ground we're treading; we used essentially the same reasoning to settle on `reading-order-items` having layout-specific keywords, rather than a generic one that could work on everything. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10333#issuecomment-2113263982 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 May 2024 19:03:31 UTC