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 May 29, 2019. It is now read-only.
Run that with the console open and you should see that when the dialog first opens, the element with id "target_container" doesn't yet exist in the DOM. If you wait a second and then click the link in the dialog, executing the code that checks for its existence, you should see that it finally exists.
I interpreted the semantics of the opened() promise as resolving after the dialog contents are "ready". But that doesn't seem to be the case? Is it a bug, or is that just not the semantics of opened()? If the latter, there doesn't seem to be any way to wait until the dialog is completely loaded and all its elements attached to the DOM.