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

Re: [webcomponents]: Building HTML elements with custom elements

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 20 Feb 2013 12:26:16 +0000
Message-ID: <CADnb78ja6bA1TKOAJkdKJ+y1eSztnam+_pgA5n0f3hQ4KiSGHg@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@chromium.org>
Cc: public-webapps <public-webapps@w3.org>, Erik Arvidsson <arv@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>, Alex Russell <slightlyoff@chromium.org>, Blake Kaplan <mrbkap@mozilla.com>, William Chen <wchen@mozilla.com>
On Tue, Feb 19, 2013 at 11:52 PM, Dimitri Glazkov <dglazkov@chromium.org> wrote:
> 3) Since the elements could derive from other existing elements, the
> localName should not be used for determining custom element's type
> (https://www.w3.org/Bugs/Public/show_bug.cgi?id=20913)
>
> PROBLEM: The localName checks are everywhere, from C++ code to
> extensions, to author code, and a lot of things will break if a custom
> element that is, for example, an HTMLButtonElement does not have
> localName of "button". Addressing this issue head on seems
> intractable.

These already cannot be just localName checks as that would mean an
element named button in some vague namespace would run through the
same code. I also fail to see exactly what the problem is here, an
example would help.


-- 
http://annevankesteren.nl/
Received on Wednesday, 20 February 2013 12:26:43 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT