W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

[Bug 26852] New: [Custom]: Specify preference of localName and typeExtension in createElement

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Sep 2014 10:00:15 +0000
To: public-webapps@w3.org
Message-ID: <bug-26852-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 26852
           Summary: [Custom]: Specify preference of localName and
                    typeExtension in createElement
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: deepak.sa@samsung.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

As specified in instantiation of custom elements that "custom tag" will take
preference over "type extension", it is required to specify the same in case of
createElement(...) .

 Element createElement(DOMString localName, DOMString typeExtension);

Here if localName is also a custom tag, then what will be the prototype of
"Element"? Will it be of typeExtension or of localName.

Consider the following case:

var xA = doc.registerElement("x-a");
var xB = doc.registerElement("x-b");

var customElement = doc.createElement("x-a", "x-b");

What should be the prototype of customElement?

AFAIK, this will be the same case as specifying:

<x-a is="x-b"></x-a>

In this case prototype will be of "x-a".

If the above theory is correct, then
test case is wrong.

If this issue has been raised earlier, then please provide the link and close
this bug.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 19 September 2014 10:00:20 UTC

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