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

I don't have a major issue with adding a flag like `isCustomElement` but I do worry about libraries/frameworks having increased branching in their code based on something like this. It's still not clear to me why it needs to be done. None of the templating engines I've written in the last ten years needed something like this, and they work fine with custom elements by treating them just like any other element.

Can we capture the library/framework use cases to better understand why this branching is needed? Perhaps there is a better way to address the specific concerns.

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

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