@caridy In situations where I’ve needed an element to be truly encapsulated, it’s also been effectively unsubclassable (because the reactions are themselves needed to be reliable/private — methods deleted after registration). I’ve just gone ahead and added a `new.target` requirement to those elements to throw the same `Illegal constructor` TypeError you’d get trying to register a subclassed native element. I’m having trouble imagining a scenario where “doesn’t have internals” is important but subclassing is actually supported, since almost any meaningfully subclassable CE already must be leaky somewhere for that to work. -- 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/871#issuecomment-677449392
Received on Thursday, 20 August 2020 08:13:29 UTC