#102550race condition in value-picker initialization
Description
(Custom) element children are not guaranteed to be available by the time
the element is added to the DOM — i.e. when the connectedCallback() is
triggered by the browser. That means we can not assume that value-picker
<select> children will always be available.</select>
Note that it worked most of the times, because JavaScript modules are
loaded asynchronously, and thus “most of the times” execute later after
the DOM is rendered, but when the server is really busy, the HTML output
can be rendered very late, so that a connectedCallback is triggered
immediately when an opening tag is written to the DOM — even before the
childrens are attached. (Otherwise the browsers would have to delay the
connectedCallback’s until the closing tag is rendered, but that’s not
the case — at least not in google chrome.)
Error:
connected-callback-children.png
Reviews 9
- 12.4 88638[BUGFIX] Fix race conditions in childnode querying custom elements
- 13.4 88637[BUGFIX] Fix race conditions in childnode querying custom elements
- main 88589[BUGFIX] Fix race conditions in childnode querying custom elements
- 12.4 82479[BUGFIX] Ensure table wizard connected callback has access to textarea
- main 82308[BUGFIX] Ensure table wizard connected callback has access to textarea
- 12.4 82169[BUGFIX] Fix link-element initialization race condition
- main 82088[BUGFIX] Fix link-element initialization race condition
- main 81993[BUGFIX] Fix value-picker initialization race condition
- 12.4 82018[BUGFIX] Fix value-picker initialization race condition