W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Base Template (Was Re: Minimum viable custom elements)

From: Ryosuke Niwa <rniwa@apple.com>
Date: Thu, 12 Feb 2015 09:46:51 -0800
Message-id: <9022159F-CA76-4B86-B8C0-29D8348BF94D@apple.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, WebApps WG <public-webapps@w3.org>
To: Steve Faulkner <faulkner.steve@gmail.com>

> On Feb 12, 2015, at 4:50 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote:
> On 12 February 2015 at 10:58, Anne van Kesteren <annevk@annevk.nl <mailto:annevk@annevk.nl>> wrote:
> which is a very different problem from what you want to solve, no?
> The problem I think needs solving for minimum viable custom elements is reducing reliance on bolt-on accessibility. From the example provided http://janmiksovsky.github.io/base-template/ <http://janmiksovsky.github.io/base-template/> it appears that in this instance it does achieve that end.
> I don't know whether this will extend to other UI controls or whether it is a practical solution, which is why I brought it to the list for discussion.

Again, this proposal or subclassing problem is nothing to do with custom elements but all do with shadow DOM.

Ironically, I've pointed out the exact same problem explained in this page last April and proposed to change the way shadow DOM works to solve it:
https://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0151.html <https://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0151.html>

- R. Niwa

Received on Thursday, 12 February 2015 17:47:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC