You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2018. It is now read-only.
@@ -121,7 +121,7 @@ This can also be used to create an instance:
121
121
xFooButton.foo(); // "foo() called"
122
122
123
123
Browser limitations require that we supply the constructor while you supply the `prototype`.
124
-
Use the `readyCallback` to do initialization work that might otherwise be in a constructor.
124
+
Use the `createdCallback` to do initialization work that might otherwise be in a constructor.
125
125
126
126
## Polyfill details
127
127
@@ -152,12 +152,12 @@ Example:
152
152
153
153
The Custom Elements specification is still under discussion. The polyfill implements certain features in advance of the specification. In particular, there are several notification callback methods that are used if implemented on the element prototype.
154
154
155
-
*`readyCallback()` is called when a custom element is created.
156
-
*`insertedCallback()` is called when a custom element is inserted into a DOM subtree.
157
-
*`removedCallback()` is called when a custom element is removed from a DOM subtree.
155
+
*`createdCallback()` is called when a custom element is created.
156
+
*`enteredDocumentCallback()` is called when a custom element is inserted into a DOM subtree.
157
+
*`leftDocumentCallback()` is called when a custom element is removed from a DOM subtree.
158
158
*`attributeChangedCallback(attributeName)` is called when a custom element's attribute value has changed
159
159
160
-
`readyCallback` is invoked _synchronously_ with element instantiation, the other callbacks are called _asyncronously_. The asynchronous callbacks generally use the MutationObserver timing model, which means they are called before layouts, paints, or other triggered events, so the developer need not worry about flashing content or other bad things happening before the callback has a chance to react to changes.
160
+
`createdCallback` is invoked _synchronously_ with element instantiation, the other callbacks are called _asyncronously_. The asynchronous callbacks generally use the MutationObserver timing model, which means they are called before layouts, paints, or other triggered events, so the developer need not worry about flashing content or other bad things happening before the callback has a chance to react to changes.
161
161
162
162
The `extends` option to `document.register()` (discussed above) is exclusive to this polyfill.
0 commit comments