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

Given that Chrome and Safari have already shipped custom elements v1 API, I don't think we can make such a backwards incompatible change now.

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

Received on Monday, 5 June 2017 22:56:41 UTC