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

No, I don't expect that browsers would want to literally implement their internals in JavaScript; preparing to oust native implementation of the DOM in C++ (for example) is absolutely a non-goal here. However, if tree building during parsing (for example) was *defined* in terms of DOM operations through the JavaScript API it would be much cleaner but allowing custom element authors to shadow these APIs while the browser doesn't actually call them for these operations means that this cleaner description will never be possible in the future.

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