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

Sure, `setAttribute` might not have anything to do with responding to the new value. I just wanted to point out that the difference in the two is strange from the perspective of someone who thinks they're just extending HTMLElement.

The parser can't be explained as
```javascript
let e = document.createElement('my-element');
e.setAttribute('a', 'b');
```
instead, it has to be closer to
```javascript
let e = document.createElement('my-element');
Element.prototype.setAttribute.apply(e, ['a', 'b']);
```
and custom elements make that much more obvious.

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