Re: [webcomponents] Imperative API for Insertion Points

2014-02-18 Thread Erik Bryn
On Mon, Feb 17, 2014 at 11:03 AM, Edward O'Connor eocon...@apple.comwrote: I think Ryosuke's content.add/remove are a better base layer than content select. In fact, content select is straightforwardly implementable / explainable on top of MO + content.add/remove, but there are several use

Re: [webcomponents] Imperative API for Insertion Points

2014-02-17 Thread Edward O'Connor
Hi Alex, You wrote: This doesn't seem like progress. I'd hope an imperative API would, instead, be used to explain how the existing system works and then propose layering that both accommodates the existing system and opens new areas for programmatic use. I think Ryosuke's

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Ryosuke Niwa
On Feb 15, 2014, at 11:30 PM, Alex Russell slightly...@google.com wrote: On Sat, Feb 15, 2014 at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote: Hi all, I’d like to propose one solution for [Shadow]: Specify imperative API for node distribution

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Ryosuke Niwa
On Feb 16, 2014, at 12:42 AM, Ryosuke Niwa rn...@apple.com wrote: On Feb 15, 2014, at 11:30 PM, Alex Russell slightly...@google.com wrote: On Sat, Feb 15, 2014 at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote: Hi all, I’d like to propose one solution for [Shadow]: Specify imperative API

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Alex Russell
On Sun, Feb 16, 2014 at 12:52 AM, Ryosuke Niwa rn...@apple.com wrote: On Feb 16, 2014, at 12:42 AM, Ryosuke Niwa rn...@apple.com wrote: On Feb 15, 2014, at 11:30 PM, Alex Russell slightly...@google.com wrote: On Sat, Feb 15, 2014 at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote: Hi all,

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Ryosuke Niwa
On Feb 15, 2014, at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote: Hi all, I’d like to propose one solution for [Shadow]: Specify imperative API for node distribution https://www.w3.org/Bugs/Public/show_bug.cgi?id=18429 because select content attribute doesn’t satisfy the needs of

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Maciej Stachowiak
On Feb 15, 2014, at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote:Hi all,I’d like to propose one solution for[Shadow]: Specify imperative API for node distributionhttps://www.w3.org/Bugs/Public/show_bug.cgi?id=18429because select content attribute doesn’t satisfy the needs of framework/library

Re: [webcomponents] Imperative API for Insertion Points

2014-02-16 Thread Ryosuke Niwa
On Feb 16, 2014, at 1:21 AM, Alex Russell slightly...@google.com wrote: On Sun, Feb 16, 2014 at 12:52 AM, Ryosuke Niwa rn...@apple.com wrote: On Feb 16, 2014, at 12:42 AM, Ryosuke Niwa rn...@apple.com wrote: On Feb 15, 2014, at 11:30 PM, Alex Russell slightly...@google.com wrote: On

Re: [webcomponents] Imperative API for Insertion Points

2014-02-15 Thread Alex Russell
On Sat, Feb 15, 2014 at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote: Hi all, I’d like to propose one solution for [Shadow]: Specify imperative API for node distribution https://www.w3.org/Bugs/Public/show_bug.cgi?id=18429 because select content attribute doesn’t satisfy the needs of