Doc in progress at
https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Type-Extensions.md
On Sat, Jun 13, 2015 at 8:50 AM, Dimitri Glazkov
wrote:
> Folks,
>
> I agree with Anne that we've been having a somewhat circular re-discovery
> of the pros/cons here. I believe that the best way t
On Tue, Jun 9, 2015 at 8:13 AM, Anne van Kesteren wrote:
> On Sun, May 10, 2015 at 12:34 AM, Alice Boxhall
> wrote:
> > - In the time between v1 and v2 (however long that ends up being) we are
> > left without any way to solve this problem, assuming we don't come up
&g
On Mon, Jun 8, 2015 at 4:23 PM, Ryosuke Niwa wrote:
>
> On Jun 8, 2015, at 3:23 PM, Alice Boxhall wrote:
>
> On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa wrote:
>
>>
>> > On Jun 8, 2015, at 2:16 PM, Alice Boxhall wrote:
>> Web developers are already writ
On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa wrote:
>
> > On Jun 8, 2015, at 2:16 PM, Alice Boxhall wrote:
> >
> > Did anyone have any further thoughts on this? My concerns haven't
> changed.
>
> Nothing new.
>
> > On Sat, May 9, 2015 at 3:34 PM, Alic
Did anyone have any further thoughts on this? My concerns haven't changed.
On Sat, May 9, 2015 at 3:34 PM, Alice Boxhall wrote:
> On Thu, May 7, 2015 at 1:00 AM, Anne van Kesteren
> wrote:
>
>> On Wed, May 6, 2015 at 6:59 PM, Alice Boxhall
>> wrote:
>> > I
On Thu, May 7, 2015 at 1:00 AM, Anne van Kesteren wrote:
> On Wed, May 6, 2015 at 6:59 PM, Alice Boxhall wrote:
> > I definitely acknowledge is= may not be the ideal solution to the latter
> > problem - it definitely has some holes in it, especially when you start
> > addin
I agree we badly need the primitives, but it seems to me like there is
potentially an easier and maybe even bigger win in making it more
straightforward for developers to reuse existing patterns (like the one you
described for "button" earlier) than in explaining the existing patterns
and allowing
On Wed, May 6, 2015 at 8:33 AM, Anne van Kesteren wrote:
> On Wed, May 6, 2015 at 4:46 PM, LĂ©onie Watson
> wrote:
> > My understanding is that sub-classing would give us the accessibility
> inheritance we were hoping is= would provide. Apologies if I've missed it
> somewhere obvious, but is ther
n
the , right? So you'd have to keep them in sync regardless.
On Wed, Feb 4, 2015 at 11:14 AM, Ryosuke Niwa wrote:
>
> On Feb 4, 2015, at 11:05 AM, Alice Boxhall wrote:
>
> On Wed, Feb 4, 2015 at 11:01 AM, Brian Kardell wrote:
>
>>
>> On Wed, Feb 4, 201
On Wed, Feb 4, 2015 at 11:01 AM, Brian Kardell wrote:
>
>
> On Wed, Feb 4, 2015 at 1:54 PM, Alice Boxhall wrote:
>
>> On Wed, Feb 4, 2015 at 10:36 AM, Ryosuke Niwa wrote:
>>
>>>
>>> On Feb 4, 2015, at 10:12 AM, Brian Kardell wrote:
>>>
On Wed, Feb 4, 2015 at 10:36 AM, Ryosuke Niwa wrote:
>
> On Feb 4, 2015, at 10:12 AM, Brian Kardell wrote:
>
> On Wed, Feb 4, 2015 at 12:41 PM, Chris Bateman
> wrote:
>
>> Yeah, I had noted in that post that wrapping a native element with a
>> custom element was an option - only drawback is tha
On Fri, Jan 30, 2015 at 8:46 AM, Anne van Kesteren wrote:
> On Fri, Jan 30, 2015 at 11:05 AM, Steve Faulkner
> wrote:
> > In this radio and checkbox example (view in chrome)
> > https://rawgit.com/alice/web-components-demos/master/index.html
> > (which has been referenced several times in this t
On Fri, Jan 30, 2015 at 8:46 AM, Anne van Kesteren wrote:
> On Fri, Jan 30, 2015 at 11:05 AM, Steve Faulkner
> wrote:
> > In this radio and checkbox example (view in chrome)
> > https://rawgit.com/alice/web-components-demos/master/index.html
> > (which has been referenced several times in this t
13 matches
Mail list logo