- From: Konnor Rogers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Nov 2024 18:58:59 +0000
- To: public-css-archive@w3.org
> Thanks for liking me the issue. What we want is `node.isWebElement` to be `true` when it's a web-element. This is differently than having `-` in the `tagName`. Is not the same to have a `-` than to be a web-element. > > The CSS selector, would be nice I guess, but when you are in a hot path, you do not want to query-selector/match anything at all, you just want to know if a given element is a web-element or not. Correct. Nothing is stopping someone from doing: `<myspecialcustomelement>` which would *technically* work, but that just becomes HTMLUnknownElement and you can never register in the custom elements registry. this issue tracker is about CSS though. I imagine this probably isn't the place to talk about `node.isCustomElement` being added to the platform. -- GitHub Notification of comment by KonnorRogers Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11001#issuecomment-2455476329 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 November 2024 18:59:00 UTC