[Bug 24087] [Custom]: Rename document.registerElement to defineElement

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24087

--- Comment #6 from Ryosuke Niwa <rniwa@webkit.org> ---
(In reply to Scott Miles from comment #5)
> I'm sorry there wasn't more clarity on the arguments. The rationale for
> 'register' goes something like this:
> 
> There was a first concept from the originators of Custom Elements, which was
> to make 'a way to attach a JS class to a element'. So, the vision has been
> toward:
> 
>   class MyElement extends HTMLElement {
>     ...
>   }
>   document.registerElement('my-element', MyElement);
> 
> From this point of view, the `class` statement is what I would consider the
> definition. From there, it seemed clear that the document method was
> registering a tag-name for that.

I don't understand this given we can't really define an element without a name.
We don' refer to an element with its IDL interface name. See
http://www.w3.org/html/wg/drafts/html/CR/dom.html#elements

Look at the very first sentence of this section:
"Elements, attributes, and attribute values in HTML are defined (by this
specification) to have certain meanings (semantics). For example, the ol
element represents an ordered list, and the lang attribute represents the
language of the content."

Here, we mention "ol" element, not HTMLOListElement.

In addition, multiple elements can share a single IDL interface; e.g. del and
ins element share single HTMLModElement. In that sense, defining an element is
synonymous to defining a tag name.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 6 February 2014 07:11:05 UTC