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

I see. Hmm. 

Technically any HTML element can have any attribute or property. And some libraries add them dynamically for their own use. So, I would tend not to rely on knowing what attrs/props anything has, as a general rule.

It also seems pretty strange to me to branch on setting an attr vs. prop the value type or inheritance hierarchy.

In general, I think the developer who is using the element should specify whether to set property, attribute, boolean attribute, etc. using some syntax in the template engine. Trying to get the templating engine to guess the right mechanism seems like it will cause problems. I'm even less sure how this will work with future potential standards like custom attributes.

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

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