This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22564 - [Custom]: Rename readyCallback to createdCallback
Summary: [Custom]: Rename readyCallback to createdCallback
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency tree / graph
 
Reported: 2013-07-03 22:28 UTC by Dimitri Glazkov
Modified: 2013-08-07 20:53 UTC (History)
7 users (show)

See Also:

Attachments

Description Dimitri Glazkov 2013-07-03 22:28:00 UTC 
I guess "ready" is not quite as descriptive as "created".
Comment 1 Steve Orvell 2013-07-04 01:12:10 UTC 
The name 'ready' is ambiguous: ready for what?

Users of Polymer (github.com/polymer) have expressed confusion about this. For example, one user suggested the need to be able to defer readyCallback based on a related state that should be resolved before the element could be 'ready'.

The name 'created' is descriptive about what has happened. The element has been created and the system is providing a notification about it.

The callback is intended to be used for initialization tasks and is a stand-in for a proper constructor.
Comment 2 Dominic Cooney 2013-07-04 01:30:04 UTC 
It seems "ready" is preferable only because it is the status quo?

I like "created." FWIW Daniel Buchner mentions an original preference for "created" here: <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22459#c11>.
Comment 3 Dimitri Glazkov 2013-08-07 20:53:45 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/a0559f51ecb7