Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

> The solution with `c.innerHTML = c.innerHTML.replace('<table', '<my-table').replace('<tr', '<my-tr')` Would trigger a lot of unnecessary DOM mutations, re-paints, FOUC, etc.

So would `is=""`, because `<tr is="some-thing">` may first render as `<tr>` until `some-thing` is ready, then it will re-render to `<some-thing>`.

---

I have a crazy but awesome idea: How about browsers take the "native" elements and re-write them entirely with JavaScript using Web Components APIs. This would make them moldable/hackable/monkey-patchable/extendable/breakable/mixinable/etc to the web developer's needs. If we did this first with problem elements (table, tr, form, input, etc), then web developers would inevitably solve the problems in various ways. Imagine the "native" (non-interpreted) side of a browser is merely a platform that allows for elements to be defined (Custom Elements), and that all pre-existing elements are merely custom elements. The used-to-be-"native" elements would still be native, just that they are defined in the browser's native JavaScript context, not the web app's context, and would still work even if javascript is "disabled". This will give us all a clear picture of how the web works and how to modify it. It would be a big undertaking, but would have awesome results.

-- 
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/509#issuecomment-266915898