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: Fri, 16 Jan 2015 17:52:40 +0100
Message-ID: <CADnb78gxdLATD+LAkq1gGe+JVGNCCD0GEs5-NKGna2hVZ5uTsg@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: "Edward O'Connor" <eoconnor@apple.com>, WebApps WG <public-webapps@w3.org>
On Fri, Jan 16, 2015 at 5:45 PM, Steve Faulkner
<faulkner.steve@gmail.com> wrote:
> I have not suggested is= as the method that must be implemented (I have not
> demanded anything), what I have tried to suggest is that minimum viable
> custom elements with all accessibility as bolt-on is a poor solution by
> design.  From an acc view it means custom elements are nothing more than
> <div>s with fancy names.

Sure, I hope everyone understands that, but do you see a viable way to
get there? Again, I think that unless we solve the styling problem for
native elements, we're not going to see them adopted, not even if you
can subclass them (and proper subclassing without the is="" hack is
another hard problem, as explained).


-- 
https://annevankesteren.nl/
Received on Friday, 16 January 2015 16:53:08 UTC

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