22564 2013-07-03 22:28:00 +0000 [Custom]: Rename readyCallback to createdCallback 2013-08-07 20:53:45 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14968 1 dglazkov dglazkov danieljb2 dfreedm dominicc mrbkap sjmiles sorvell wchen public-webapps-bugzilla oldest_to_newest 90277 0 dglazkov 2013-07-03 22:28:00 +0000 I guess "ready" is not quite as descriptive as "created". 90313 1 sorvell 2013-07-04 01:12:10 +0000 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. 90314 2 dominicc 2013-07-04 01:30:04 +0000 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>. 91745 3 dglazkov 2013-08-07 20:53:45 +0000 https://dvcs.w3.org/hg/webcomponents/rev/a0559f51ecb7