Re: [w3c/webcomponents] HTMLElement.prototype needs to define the custom element callbacks. (#582)

We've talked about this before. The problem was always figuring out what they should do. E.g. should HTMLTemplateElement.prototype.adoptedCallback perform the adopting steps for template? Is that really something we want to expose to user code arbitrarily? Probably not, but then, is it weird to have HTMLTemplateElement.prototype.adoptedCallback do absolutely nothing, despite the fact that template elements have important adoption semantics?

Perhaps a less-esoteric example is HTMLInputElement.prototype.attributeChangedCallback.

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