I think I would rather browser vendors come up with a source maps-like solution for DOM rather than custom elements and Shadow DOM
-
-
Replying to @ErikArvidsson
@ErikArvidsson Interesting idea. I think@ebryn is suggesting that API design is better approached in libraries in user space.2 replies 0 retweets 0 likes -
Replying to @sebmarkbage
@sebmarkbage And I'm suggesting@ebryn doesn't understand the idea behind web components. See http://extensiblewebmanifesto.org/ for background2 replies 0 retweets 1 like -
Replying to @ErikArvidsson
@ErikArvidsson Well aware of it. You might have noticed two of my fellow Ember core team signers on that list@sebmarkbage2 replies 0 retweets 0 likes -
Replying to @ebryn
@ebryn@ErikArvidsson ship register first, then add features to the element. How the EWM would want it@sebmarkbage2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats As you know custom elements aren’t my fave, my MVP wish list would be scoped CSS and <template>@ErikArvidsson@sebmarkbage2 replies 1 retweet 0 likes
@ebryn @ErikArvidsson @sebmarkbage both of those are separated and already landed ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.