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. I provided the overarching
"As a developer" user stories that clearly describe, without technical
definition, the desired flows and pain points a solution should optimize
for. A use case is a more technical, specific application scenario that
describes a desired output.

I also submitted a use case or two (one being a button with an icon and
custom events) for assessment against those user stories. I'd like to see
folks run the litany of use cases presented here through the empirical,
objective user stories that have already been submitted.

On Feb 22, 2017 11:10 PM, "Ole Ersoy" <notifications@github.com> wrote:

accounts to come up with solution that is broad-sweeping. The use case:
Allow developers to build custom elements with all the same affordances,
conveniences, and behaviors to built-ins.

I don't think anyone disagrees with this.

Requiring a user-story other than
this is a political movement that we all know will block or stall progress
on this issue for YEARS if not indefinitely.

We all want Aladdins Lamp. Everyone agrees that this is the ultimate end
game. The point of having concrete real world user stories in addition to
this end game is to ensure that we have real world test cases to verify
progress against. It's possible to approach this from both ends. Personally
I have a much easier time looking at something concrete, and then
extrapolating what the API should be from there. For example take this
boostrap markup from the dropdown example
<http://getbootstrap.com/components/#dropdowns-example>:

<div class="dropdown">
  <button class="btn btn-default dropdown-toggle" type="button"
id="dropdownMenu1" data-toggle="dropdown" aria-haspopup="true"
aria-expanded="true">
    Dropdown
    <span class="caret"></span>
  </button>
  <ul class="dropdown-menu" aria-labelledby="dropdownMenu1">
    <li><a href="#">Action</a></li>
    <li><a href="#">Another action</a></li>
    <li><a href="#">Something else here</a></li>
    <li role="separator" class="divider"></li>
    <li><a href="#">Separated link</a></li>
  </ul>
</div>

This would be far more elegant as a few custom elements. So what is the API
for creating those elements? What native capabilities should these elements
inherit? Do they need everything that the native element has or is it
better to use mixins to allow for precise features / behaviors?

The point of a simple concrete use case is not to stand in the way of
Aladdins Lamp. It's to evaluate ways to get the lamp. Once we look at this
long enough the best way to get the lamp will be obvious, but we have to
start looking at concrete real world cases, otherwise we will be stuck in
this Mad Hatter world forever. GIVE ME THE LAMP!!!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/w3c/webcomponents/issues/509#issuecomment-281913141>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAICyhBK7wKaYkTif2pKSh9PFk6Xvf2cks5rfTDMgaJpZM4Iq2sA>
.


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