@wiredearp > your specific suggestion would break the web in production Not necessarily, because not all browsers even support `is=""` natively yet (Safari for example). Some apps might break, but those apps are currently relying on not-yet-fully-official functionality (it is spec'd, but it isn't official if not all browsers want to implement it). If we were to change the spec, and all browsers wanted to implement the new spec, then it'd be official. That said, I'm open to the idea of using an alternate name other than `is=""`. THe concept itself is the main idea here, which I think is much better than what the current `is=""` spec provides. -- 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/662#issuecomment-327680552
Received on Thursday, 7 September 2017 04:23:39 UTC