- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Aug 2022 21:23:15 +0000
- To: public-css-archive@w3.org
Carrying around implicit source information that isn't textually reflected in any way isn't great. We ended up doing it for shadow-scoped names, for example, and while I think we ended up on the best overall solution, it's still not great that a no-op that set the current style to itself can actually change the meaning of the style (by changing the tree that you're looking up the reference in). I'd personally strongly prefer a textual mechanism to differentiate the two. That also avoids problems with scripting APIs, as you listed in the OP, which would need to carry the source data out-of-band. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7560#issuecomment-1227775562 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 August 2022 21:23:17 UTC