> On May 21, 2015, at 11:33 PM, Wilson Page wrote:
>
> From experience building components for Firefox OS I think the 'default slot'
> pattern will fulfill most of our use-cases. This means we won't have to
> burden our component users by requiring them to add `slot="foo"` all over the
> plac
>From experience building components for Firefox OS I think the 'default
slot' pattern will fulfill most of our use-cases. This means we won't have
to burden our component users by requiring them to add `slot="foo"` all
over the place.
Is it fair to say that if this declarative API lands in V1, it
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27727
Joshua Bell changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
Since this is public now for everybody, please let me give some
additional information.
We think that the extraction mechanisms described in the patent and not
covered by any spec will happen one day too, and could be integrated in
the Web Components spec, the purpose being to extract a customized
On Thu, May 21, 2015 at 10:22 AM, Travis Leithead <
travis.leith...@microsoft.com> wrote:
> This works for me too.
>
> And I like the proposed new bikeshed-ed names Anne suggests below.
>
SG. Started a proposal stub here:
https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Slots-Proposal
This works for me too.
And I like the proposed new bikeshed-ed names Anne suggests below.
-Original Message-
From: Anne van Kesteren [mailto:ann...@annevk.nl]
Sent: Wednesday, May 20, 2015 9:10 PM
To: Dimitri Glazkov
Cc: Scott Miles; Ryosuke Niwa; Edward O'Connor; Travis Leithead; Maciej
