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.

No, you're right, don't talk yourself out of this. I think it is important that we honor [The Extensible Web Manifesto](https://github.com/extensibleweb/manifesto).

> - Expose low-level capabilities that explain existing features, such as HTML and CSS, allowing authors to understand and replicate them.

```js
customElements.define('my-element', class extends HTMLElement {
  setAttribute() {
    // Do nothing.
  }
});
```

^ That should in fact do nothing! If it did nothing, it would *explain the web better*, which I think is simple enough reason to make this change. We can achieve this by (re)writing the native interfaces so that they behave *as if* they were written in JavaScript.

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