- From: Andrea Giammarchi <notifications@github.com>
- Date: Thu, 18 May 2017 02:46:40 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/webcomponents/issues/509/302355827@github.com>
> Are there (medium+ sized) React Apps that have no-JS fallbacks React renders on the server too so ... **yes**. > So why should webcomponents support more if web standards are limited to whatever is already out there and works already in any browser I guess we can all go home now and stop bothering each other. We don't need innovation here. On top of that, I use [a different stack](https://github.com/WebReflection/hyperHTML) and I don't use React at all, neither I am advocating for it; quite the opposite, I've said we're losing against it because while React has back-end rendering too, the equivalent of an HTML only fallback without JS on top in this case, we're still bla-bla-blahing about something loudly asked by developers, ignored by vendors, without a single, concrete, proposal, to have graceful enhance and enrich native elements. the `HTMLInputElement` is broken, and so is the `HTMLButtonElement` one and every other. There is an inconsistent behavir approved by everyone that is not fxing, rather ignoring, every other thing already available in the Web platform. I so much wish I could stop wining about this situation, yet nobody has proposed a way to extend native components. Did I mention I'd like to extend native components otherwise Custom Elements give us pretty much nothing more than a glorified CSS selector by name an a MutationObserver to deal with the DOM ? > ... it would work just as well in a browser supporting it ... Let me try to clarify this. The **14th of May 2013** the [First Public Working Draft](https://www.w3.org/TR/2013/WD-custom-elements-20130514/) about Custom Elements was published. That's, today, more than 4 years ago, this is the current situation abut Custom Elements.  Do I really need to post a Gene Wilder meme here? Can we be realistic about the fact Chrome still support V0 and the `is=""` and products using it already shipped? Did I mention production websites already used `is=""` and it simply worked? Is there any alternative proposal about extending native components in a way `is=""` did already for years on the plate? Yes? That is AWESOME! No? ... and why is that? -- 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-302355827
Received on Thursday, 18 May 2017 09:47:13 UTC