- From: Tab Atkins Jr. <notifications@github.com>
- Date: Wed, 08 Mar 2023 14:38:45 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 March 2023 22:38:58 UTC
> Fields shouldn't contain the name of the concept they belong to. I don't think this is at all universal - we *often* put the parent term into sub-definitions, for readability. We'll often put in a local-lt without the prefix, so it's not too repetitious in the spec itself, which is most likely to say it a bunch and have the context already, but that's it. > I would be glad to have CSS configured to prefer its own terms internally somehow if that's possible; @tabatkins is that possible? (Splitting into modules is useful to us in a lot of ways but it definitely makes cross-linking more of a mess.) It's not currently possible; it would require some categorization and logic that does not exist currently. Probably something I want eventually, but still needs a lot of thought to make it more than just "something for the CSSWG to use". -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1168#issuecomment-1460982878 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1168/c1460982878@github.com>
Received on Wednesday, 8 March 2023 22:38:58 UTC