- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Feb 2014 00:08:14 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24087
Ryosuke Niwa <rniwa@webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rniwa@webkit.org
--- Comment #4 from Ryosuke Niwa <rniwa@webkit.org> ---
(In reply to Dominic Cooney from comment #0)
> Based on the thread starting here:
> <http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0968.html>,
> document.register should be renamed to document.registerElement. It's more
> specific about what this method does, lines up with other "register" methods
> (eg registerProtocolHandler)
I don't think we should line the name up with registerProtocolHandler. As far
as I understand, registerProtocolHandler permanently associates a URL with a
given protocol. The registration doesn't go away simply because the page that
made it got closed. In comparison, custom elements are NOT persistent across
sessions.
> Retains an imperative flavor (since it may trigger callbacks.)
I don't know why "register" is considered more imperative than "define". Both
of them are verbs.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 6 February 2014 00:08:16 UTC