Re: Base Template (Was Re: Minimum viable custom elements)

Jan,

As for the following, in https://github.com/JanMiksovsky/base-template),
> A web component spec bug
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=22344> tried to resolve
this question by fixing the platform, but an initial Blink implementation
<https://code.google.com/p/chromium/issues/detail?id=263701> ran into
problems and had to be backed out. This problem is unlikely to be resolved
at the platform level anytime soon,

This is correct.  Although I've not given up speccing and implementing
"shadow as a constructor call for the super class" again,  but it won't
happen anytime soon.

On Sat Feb 14 2015 at 2:46:22 AM Jan Miksovsky <jan@component.kitchen>
wrote:

> Dimitri: Okay, I can follow up with Ryosuke. I’m happy to share our
> thoughts and needs for subclassing components.
>
> Anne/Steve: I’d originally indicated that this technique couldn't be
> applied to extending native HTML elements. Since the two of your seemed
> interested in that, I spent some time tinkering with the idea, and it turns
> out that this technique can be made to work for that situation. I’ve posted
> a quick demo (
> http://janmiksovsky.github.io/base-template/extendButton.html) showing
> subclassing of a standard HTML button element. This works best under native
> Shadow DOM. Under polyfilled Shadow DOM, base class styles can’t (yet?) be
> inherited.
>
> Anyway, I mention this in case it opens up some ideas. Thanks for the
> inspiration!
>

Received on Monday, 16 February 2015 05:35:59 UTC