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

2013-12-11 Thread Matthew McNulty
On Tue, Dec 10, 2013 at 4:04 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 9:34 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 11:13 AM, Scott Miles sjmi...@google.com wrote: I'm not wont to try to summarize it here, since he said it already better there. Perhaps

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

2013-12-10 Thread Ryosuke Niwa
Let's take a look at the original list of use cases proposed in 2008 at http://www.w3.org/2008/webapps/wiki/Component_Model_Use_Cases: Layout Manager Layout Manager Use Case Parameters Who Web Framework Engineer What Build a layout library, consisting of a UI layout primitives, such as panel,

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

2013-12-09 Thread Ryosuke Niwa
On Dec 9, 2013, at 9:34 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 11:13 AM, Scott Miles sjmi...@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.

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

2013-12-09 Thread Ryosuke Niwa
On Dec 9, 2013, at 11:03 PM, Matthew McNulty mmcnu...@google.com wrote: On Tue, Dec 10, 2013 at 4:04 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 9:34 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 11:13 AM, Scott Miles sjmi...@google.com wrote: I'm not wont to try