W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Component Model: Landing Experimental Shadow DOM API in WebKit

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 30 Jun 2011 10:59:55 -0700
Cc: public-webapps <public-webapps@w3.org>
Message-id: <906F0574-9315-4810-97D3-ADA5CEE43531@apple.com>
To: Dimitri Glazkov <dglazkov@chromium.org>

On Jun 29, 2011, at 9:08 AM, Dimitri Glazkov wrote:

> Hi Folks!
> With use cases (http://wiki.whatwg.org/wiki/Component_Model_Use_Cases)

So I looked at this list of use cases. It seems to me almost none of these are met by the proposal at <http://dglazkov.github.com/component-model/dom.html>.

Can you give a list of use cases that are actually intended to be addressed by this proposal?

(I would be glad to explain in more detail why the requirements aren't satisfied in case it isn't obvious; the main issues being that the proposal on the table can't handle multiple bindings, can't form controls, and lacks proper ("type 2") encapsulation).

These use cases are also, honestly, rather vague. In light of this, it's very hard to evaluate the proposal, since it has no obvious relationship to its supporting use cases.

Could we please get the following to be able to evaluate this component proposal:

- List of use cases, ideally backed up with very concrete examples, not just vague high-level statements
- Identification of which use cases the proposal even intends to address, and which will possibly be addressed later
- Explanation of how the proposal satisfies the use cases it is intended to address
- For bonus points, explanation of how XBL2 fails to meet the stated use cases

Received on Thursday, 30 June 2011 18:00:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:20 UTC