Component Model f2f: Actionable things

You can see the minutes here: http://www.w3.org/2011/11/02-webapps-minutes.html

First of all, thank you all for coming and participating. It was
exhausting, and we just ran out of time. Stupid time!

There was also a great conversation post-meeting, but unfortunately no
minutes :(

Things to act on as I see them, in random order -- please add your own:

PROBLEM: Peeps hate constructable DOM elements. I saw uniform allergic
reaction to HTMLElement.call across the browser- and spec-folk.
ACTION: sugar this up as a declarative syntax and lead with that.

PROBLEM: There is a strong desire for a simple answer to the consumer
use case: "I like your component library and would like to use it. How
do I do that?"
ACTION: come up with a strong declarative proposal which explains
that, build consensus and turn it into a spec.

PROBLEM: Cross-origin components are a big deal and should not be
waved off as something to do later.
ACTION: Write confinement/isolation proposal, build consensus and turn
it into a spec.

PROBLEM: Currently, decorators are not part the component model.
There's a strong desire to satisfy at least some use cases that
decorators enable (binding with CSS, dynamic attachment/detachment)
ACTION: Come up with a decorator proposal -> consensus -> spec.

PROBLEM: I want to play with this before I can tell if it's good.
ACTION: provide an experimental build to play with as soon as possible.

PROBLEM: It's hard to see how shadow DOM can stand on its own or why
that would be useful.
ACTION: write shadow DOM spec, including examples on how it can be used.

PROBLEM: What is this I don't even
ACTION: lol

:DG<

Received on Thursday, 3 November 2011 01:41:48 UTC