Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)

@rniwa  a good compelling reason is that you can special case all native elements properties vs attributes, but you cannot do the same for custom elements, as pretty much custom elements do whatever they want. So there's a very big difference. Btw, as far as I remember Safari doesn't support `is` so I suppose that doesn't bother you. :)

The real compelling reason: every single framework has some sort of "isCustomElement" function or some "includes('.')", that should be reason enough already.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1080#issuecomment-2417739846
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1080/2417739846@github.com>