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

RE: [webcomponents] How about let's go with slots?

From: Domenic Denicola <d@domenic.me>
Date: Tue, 19 May 2015 17:59:25 +0000
To: Dimitri Glazkov <dglazkov@google.com>
CC: Elliott Sprehn <esprehn@chromium.org>, Justin Fagnani <justinfagnani@google.com>, "philip@philipwalton.com" <philip@philipwalton.com>, "dfreedm@google.com" <dfreedm@google.com>, "sjmiles@google.com" <sjmiles@google.com>, "rniwa@apple.com" <rniwa@apple.com>, "eoconnor@apple.com" <eoconnor@apple.com>, "annevk@annevk.nl" <annevk@annevk.nl>, "travis.leithead@microsoft.com" <travis.leithead@microsoft.com>, "mjs@apple.com" <mjs@apple.com>, "arronei@microsoft.com" <arronei@microsoft.com>, "slightlyoff@google.com" <slightlyoff@google.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13697D317DFDA710533852F5DFC30@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: Dimitri Glazkov [mailto:dglazkov@google.com] 

> Not sure what you mean by "Polymer model".

I was referring to Elliot's "This is identical to the common usage today in polymer apps where you annotate your own element with classes."

> When we have custom elements, the assumption of dumb containers simply goes out of the window.

I don't think it has to, as I showed in my message.

Received on Tuesday, 19 May 2015 17:59:54 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC