- From: James Browning via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Apr 2022 03:14:27 +0000
- To: public-houdini-archive@w3.org
> Uniquifying names continues to be the only reasonable solution to this, and nothing we can do to help with uniquification seems like it would be significantly better than just hand-uniquifying I still think lexical names would help, like prepending the component name definitely won't help in the presence of [scoped element registries](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md), in such places the only reliable way to uniqify is to either include some global url (i.e. `--myorg.tld/some-component--property`) or use some uuid `--401db1cf-some-property`, both of which are incredibly unweildly. Lexical names as I've suggested above, would simplify things considerably by just allowing people to use `$whateverNameTheyWant` and have it scoped to the appropriate file. -- GitHub Notification of comment by Jamesernator Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/939#issuecomment-1107696231 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 24 April 2022 03:14:28 UTC