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

> Let's not confuse user stories with use cases. 

We want a factory to build anything.  Lets at least try to build a car and a motorcycle with the prototype for that factory, and lets watch the parts flow through the routing (API) to make sure everyone likes what they see.

> (one being a button with an icon and
custom events) 

Where's the markup?  This is important because it will end up driving the workflow for web / html developers.  The two core things we are trying to do here is provide us (The component makers) with the flexibility to make the best components we can for the broadest audience (Folks that need screen readers, etc.) while at the same time providing the simplest most effective workflow for the html developers that are going to put these new components / elements to use, as well as the developers that will be maintaining this work.

-- 
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-282099610