[webcomponents] Standard Use Case (Was Auto-creating shadow DOM for custom elements)

On Dec 9, 2013, at 9:34 PM, Ryosuke Niwa <rniwa@apple.com> wrote:

> On Dec 9, 2013, at 11:13 AM, Scott Miles <sjmiles@google.com> wrote:
>> I'm not wont to try to summarize it here, since he said it already better there. Perhaps the short version is: nobody knows what the 'standard use case' is yet.
> 
> How is that possible given we've already spent 2+ years on the whole web components effort?

I don't want to start a word game here but if it's really true that we don't know what web components' the primary/standard use case is, then we have a much bigger issue here.

We need to design features and APIs to address specific use cases.  We don't design an API in the hope that that it'll magically address some use cases.

- R. Niwa