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

Re: Minimum viable custom elements

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 29 Jan 2015 16:37:25 +0100
Message-ID: <CADnb78jy72yFXSWBXDm2QMwbs3q6nR3ZsoC7H6tKSV9a6n4o9w@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: "Edward O'Connor" <eoconnor@apple.com>, WebApps WG <public-webapps@w3.org>
On Thu, Jan 29, 2015 at 3:54 PM, Steve Faulkner
<faulkner.steve@gmail.com> wrote:
> I don't have enough technical understanding to know what is viable or not,
> you and others are saying that the current accessibility feature support
> baked in to custom elements spec via is= is not acceptable

That seems rather disingenuous. I have said these things:

1) Compared to <my-element> the is="" construct is a hack that is
unlikely to be attractive to those building libraries. Existing
libraries seem to support this.

2) As long as the styling problem for form controls remains unsolved,
making some form of automatic prototype mutation work for them is not
going to get them adoption.

Others have already explained how turning 1) around is hard as
browsers, specifications, and stylesheets branch on local name rather
than instance checks. 2) is even harder and has always been the real
problem.


-- 
https://annevankesteren.nl/
Received on Thursday, 29 January 2015 15:37:48 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC