@MT Wow, I was a total newb back then. xD It says in the last comment
For example, search engines wouldn’t be able to determine how to process the files that used these new features.
I guess this is true, but is it really that important? Suppose someone, using the suggestion here coupled with the ShdowDOM idea I linked to in the opening post, defines an element
Arguably, at this point it doesn’t even matter because the
If someone goes and turns a SPAN element into some video player at the top level,
nodes.map(n => console.log(n) is still easy to understand).
Someone might really really like to use
I love Divs and use them all the time!
Someone might hate single letter elements, so
<anchor>This is a link.</anchor>
A simple component might use a 3D library (disclaimer, I’m working on it) that has MotorHTMLScene and MotorHTMLNode element classes, and it could then be convenient to use them like this:
myComponentShadowRoot.registerElement('mesh', MotorHTMLMesh) // this one doesn't exist yet
<h1>A 3D scene:</h1>
<s style="width: 600px; height: 400px;">
<n rotation="0, 30, 0" onUpdate="rotation++">
<span>This text rotates and has some decorative mesh behind it!</span>
<n translation="0 0 -200">
I dislike having to do things like
<x-box> just because I had to add a hyphen to the name of an element who’s purpose can be described using a single word word.
Let’s let authors enjoy their programming experience by letting them have more flexibility and customizability!