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

I hope it's not too late to bring this up again but I think its worth revisiting. The point is the same, this is about allowing the things the browser does internally to be described using the same APIs as those which are exposed to users. Particularly, by allowing custom element authors to shadow built in API, it becomes implicitly true that the internal implementation of the browser (the parser's tree construction, stuff that elements defined in the HTML spec do, etc.) can't be described in these terms and makes rationalizing the observable results more complicated.

-- 
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-306306262