ryansolid / dom-expressions

A Fine-Grained Runtime for Performant DOM Rendering
MIT License
885 stars 127 forks source link

Add ability not to treat every tag with `-` in name as web component #290

Open MrFoxPro opened 12 months ago

MrFoxPro commented 12 months ago

I tried to use custom tag names for better debugging, but solid treats them as web components, and, for example, data-* attribues don't work: https://playground.solidjs.com/anonymous/7c8c3bd2-59ed-49f1-bb5d-f86d8ed1df14 I wish to have ability to disable this behaviour in babel options.

chiefcll commented 6 months ago

Are you using a universal renderer? Seems like you're trying to render non html elements and additionally you want to override the HTML spec for webcomponents for - to be something other than a custom element? I assume you'd only want to do this when building a custom renderer?

For HTML you have inspector for easy debugging.

MrFoxPro commented 6 months ago

Are you using a universal renderer? Seems like you're trying to render non html elements and additionally you want to override the HTML spec for webcomponents for - to be something other than a custom element? I assume you'd only want to do this when building a custom renderer?

For HTML you have inspector for easy debugging.

No, I'm not using universal renderer. Could you please point to the statement in specification that any HTML tag with dash between words is automatically considered as Custom element? AFAIK any tag is considered as HTMLElement in all browsers, and could be upgraded to Custom elements with JavaScript.

chiefcll commented 6 months ago

https://stackoverflow.com/questions/22545621/do-custom-elements-require-a-dash-in-their-name

MrFoxPro commented 6 months ago

https://stackoverflow.com/questions/22545621/do-custom-elements-require-a-dash-in-their-name

Dash in the name is necessary but not enough for browser to treat tag as custom element