- From: Andrea Giammarchi <notifications@github.com>
- Date: Mon, 20 Feb 2017 08:52:27 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 20 February 2017 16:53:08 UTC
@matthewrobb `:implements(input-like) {}` would be already an improvement, IMO, but it touches a mined territory 'cause it has to avoid confusion with possible `implements` reserved word in JS. If we drop things that has to be defined in 3 different places (HTML, CSS, and JS counter part) whatever it is will ship sooner than later, which is IMO essential. Semantically speaking you also define an `extension`, not an interface ... so it's already a bit misleading to say you implements 'button-like' when this is defined as extension that implements itself other traits/interfaces/mixins. That being said, I'd like to understand what browser vendors have in mind (if anything) and ideally an ETA accordingly with the decision (I'm honestly tired to wait for this to ship and 3rd parts frameworks already won here because nothing is happening on the standard side). Regards -- 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-281129790
Received on Monday, 20 February 2017 16:53:08 UTC