- From: Domenic Denicola <d@domenic.me>
- Date: Mon, 18 May 2015 22:45:27 +0000
- To: Dimitri Glazkov <dglazkov@google.com>, Scott Miles <sjmiles@google.com>, Ryosuke Niwa <rniwa@apple.com>, Edward O'Connor <eoconnor@apple.com>, "Anne van Kesteren" <annevk@annevk.nl>, Travis Leithead <travis.leithead@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, "Arron Eicholz" <arronei@microsoft.com>, Alex Russell <slightlyoff@google.com>
- CC: public-webapps <public-webapps@w3.org>
From: Dimitri Glazkov [mailto:dglazkov@google.com] > What do you think, folks? Was there a writeup that explained how slots did not have the same performance/timing problems as select=""? I remember Alex and I were pretty convinced they did at the F2F, but I think you became convinced they did not ... did anyone capture that? My only other contribution is that I sincerely hope we can use tag names instead of the content-slot attribute, i.e. <dropdown> instead of <div content-slot="dropdown">. Although slots cannot fully emulate native elements in this manner (e.g. <select>/<optgroup>/<option>), they would at least get syntactically closer, and would in some cases match up (e.g. <details>/<summary>). I think it would be a shame to start proliferating markup in the <div content-slot="dropdown"> vein if we eventually want to get to a place where shadow DOM can be used to emulate native elements, which do not use this pattern.
Received on Monday, 18 May 2015 22:46:02 UTC