Re: [w3c/webcomponents] customElements.define should throw on registration of definitions that shadow built-in properties / methods. (#583)

After giving it a few days, I think I've mostly talked myself out of this. The concern was less about why it would be useful but how the implementation has to be justified given what's observable from the outside. Custom elements are going to take something that I thought might have been obscure enough to be changed for the better and put a spotlight on it. Maybe there are lots of people out there that patch over these properties on built-in elements? I suppose this is why the lifecycle callbacks are permanently stored during definition.

-- 
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/583#issuecomment-252538361