- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jan 2024 21:00:42 +0000
- To: public-css-archive@w3.org
> ACTION: TabAtkins to look into using a more generic term than 'nested' for the flag for mixed declaration+rule contexts
Closing the loop on this action:
Most of the "consume" algorithms use the "nested" flag. In almost all cases it really *does* mean "am I nested in a {} block", because it's used to determine whether a `}` stops the parsing immediately (because it's the closing brace of a parent block) or not.
The only exception is in "consume a qualified rule": in addition to the above-described usage, it's also used to decide how to handle a custom property. In theory this is referencing the "mixed declarations and rules, or just rules" decision, but in practice it's to make a custom property showing up at the top level of a stylesheet work better (so it doesn't consume the entire rest of the stylesheet), so it's *actually* caring about nesting too.
So, I'm concluding that "nested" is still an appropriate name for this flag, and this action needs no further change.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9336#issuecomment-1877754115 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 January 2024 21:00:45 UTC