Currently the waitForSelector method does not work as expected, the method never fails since the validation of the while loop is not precise (this.#celestial.DOM.querySelector() always returns an object even if the node is not found).
Therefore, this change suggests a modification in the validation and the implementation of a custom timeout by the user.
Currently the
waitForSelector
method does not work as expected, the method never fails since the validation of the while loop is not precise (this.#celestial.DOM.querySelector()
always returns an object even if the node is not found).Therefore, this change suggests a modification in the validation and the implementation of a custom timeout by the user.