- From: OvermindDL1 <notifications@github.com>
- Date: Tue, 06 Dec 2016 11:00:26 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 6 December 2016 19:01:09 UTC
> How about we fix that then? It's a spec and we are in new territory either way. It's like putting an addition on the house. We can change the spec. Maybe tear out the kitchen. Etc. As long as it is backwards compatible enough to allow progressive enhancement enough that old non-js browsers can still be supported without needing to write duplicate custom sites for them. I.E., a <button>, no matter how it is subclassed, **must** be a <button> in the html, regardless of whatever other attributes it may have. -- 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-265239690
Received on Tuesday, 6 December 2016 19:01:09 UTC