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:20:51 +0000
Message-ID: <CADnb78g49+V42wjwsqibfgfqgeFn1rusE+-c6dJV6OW0YhTpmg@mail.gmail.com>
To: Scott Miles <sjmiles@google.com>
Cc: Dimitri Glazkov <dglazkov@chromium.org>, public-webapps <public-webapps@w3.org>, Erik Arvidsson <arv@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>, Alex Russell <slightlyoff@chromium.org>
On Wed, Feb 20, 2013 at 3:01 AM, Scott Miles <sjmiles@google.com> wrote:
> Perhaps one other COST of the localName issue is the question of
> document.createElement.
> document.createElement('x-button') creates <button is='x-button'>, people
> complain because the tag names do not match.
> document.createElement('button').setAttribute('is', 'x-button'), doesn't
> work this way, "is" is not a standard attribute (according to me)
> document.createElement('button', 'x-button'), now I cannot encode my tag in
> a single variable (i.e. document.createElement(someTag))
> document.createElement('button/x-button'), I just made this up, but maybe it
> would work.

I think ideally we do none of these and just advocate using a
constructor. The setAttribute() variant can never work. The others
could work, but I don't see the point of enhancing an API we don't
envision using in the long run.)

Received on Wednesday, 20 February 2013 12:21:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC