Enqueueing custom element reactions is ineffective for customized built-in elements

[dominiccooney]

Enqueue a callback reaction step 4 says:

Let definition be the entry in registry with name equal to element's local name.

This will not find a definition for customized built-in elements because their local names (for example, "button") are not valid custom element names, hence no such definition exists.

Given the idea that changing an element's "is" attribute does not affect its behavior, this points to the need for extra state associated with the element which remembers the original value of "is" for lookups like this.

[domenic]

It seems like this is just a simple typo and it should be "with local name equal to element's local name"?

[dominiccooney]

That doesn't work for customized built-in elements; you might have <button is="pet-kittens"> and <button is="launch-missiles">; these definitions have the same local name but you want to pick a specific one and not get them mixed up.

[domenic]

Ah of course; thank you.

I guess everything is leaning toward storing an extra piece of state on the element. I'll try to make that change soon...