Re: [webcomponents] Imperative API for Insertion Points

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 <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 cases that <content>.add/remove address that are
difficult or impossible with <content select> (as described in Maciej's
recent email on this thread).


Received on Monday, 17 February 2014 19:04:18 UTC