- From: <bugzilla@jessica.w3.org>
- Date: Sat, 22 Dec 2012 00:01:03 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20487
Bug ID: 20487
Summary: [Custom]: Creation of custom elements via
createElement is underdefined
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: bzbarsky@mit.edu
QA Contact: public-webapps-bugzilla@w3.org
CC: wchen@mozilla.com
Blocks: 14968
Consider this script:
var proto = { myProp: 1 };
proto.__proto__ = HTMLElement.prototype;
var fun = document.register("x-foo", { prototype: obj });
var elem1 = document.createElement("x-foo");
var elem2 = document.createElement("X-FOO");
var elem3 = document.createElementNS(null, "x-foo");
var elem4 = document.createElementNS(null, "X-FOO");
var elem5 = document.createElementNS("http://www.w3.org/1999/xhtml",
"x-foo");
var elem6 = document.createElementNS("http://www.w3.org/1999/xhtml",
"X-FOO");
as far as I can tell, the specification does not define which of those
elements, if any, have "proto" as their proto, nor whether it depends on
whether "document" is an HTML document or an XML/XHTML document.
This is not a hypothetical problem: we just had two implementors who were
trying to guess what the spec might maybe mean here write two different
incompatible implementations.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 22 December 2012 00:01:05 UTC