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

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

Dimitri Glazkov <dglazkov@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[Custom]: Rename            |[Custom]: Rename
                   |document.registerElement to |document.register to
                   |defineElement               |registerElement

--- Comment #7 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to Maciej Stachowiak from comment #3)
> Reopening to reconsider defineElement.

Please don't rename the bug that already has a commit on it. Makes difficult to
figure out what's happening.

> 
> I gave a bunch of rationale on the list for why defineElement was better
> than registerElement:
> http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/1026.html
> 
> Many people agreed, including Dominic from Google:
> http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/1032.html
> 
> The only rationale you gave for registerElement instead is this:
> > Played with both. registerElement fit a bit better with the rest of the narrative.
> 
> Can you please either adopt defineElement or give some substantive reasoning
> for why my arguments are wrong? I don't find "played with both" or "fit
> better with the rest of the narrative" very convincing.

The "element registration is a process of adding an element definition to a
registry":
http://w3c.github.io/webcomponents/spec/custom/#dfn-element-registration 

On the other hand, "Defining an element" (or defineElement) would be the act of
constructing a definition, which doesn't quite hit the spot.

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

Received on Thursday, 6 February 2014 18:04:33 UTC