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

I think the import vs. clone node issue was discovered to be Chrome-only. That has been reported to Chrome as well, and I expect they will fix it. So, I'm not sure that should be taken into consideration, as it will be a non-issue across the board soon. Also, it's generally a bad idea to try to customize implementations based on point-in-time browser-specific perf. These things change quite a lot and often come back to bite.

Can you go into detail on what is happening around heuristics? What is being done differently for custom elements that doesn't apply to built-ins?

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

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