- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Oct 2024 23:04:07 +0000
- To: public-css-archive@w3.org
To a little clearer, since @fantasai was confused in some personal conversation: Right now, per spec, you can say `display: attr(foo ident)` and `<div foo=block>` will work. In the new resolved syntax, that would be `display: attr(foo <ident>)`. But under the new syntax you could *also* say `display: attr(foo block | flex | grid)` to allow only *those specific three keywords*. That's the ambiguity with `px`/etc that I'm worried about here. If we just go with the resolution exactly as stated in the f2f, then writing `attr(foo px)` means "attempt to parse the foo attribute as the ident `px`, and if successful, substitute that in". I still think we can probably just drop that functionality entirely in favor of using calc(), but if we did want to preserve it, I think we'd do it with some special syntax on the number production, like `<number px>` to mean "parse this as a number, then give it the px unit". -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11034#issuecomment-2412484972 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 October 2024 23:04:08 UTC