Timothy Flynn 5fe499b493 LibWeb+WebContent+WebDriver: Asynchronously wait for dialog dismissal ... There was a timing issue here where WebDriver would dismiss a dialog, and then invoke another endpoint before the dialog was actually closed. This is because the dismissal first has to hop over to the UI process to close the graphical dialog, which then asynchronously informs WebContent of the result. It's not until WebContent receives that result that the dialog is considered closed, thus those subsequent endpoints would abort due a dialog being "open". We now wait for dialogs to be fully closed before returning from the dismissal endpoints. (cherry picked from commit 0722a3b1c091adbafc056686ebedbf5c2db84207)		2024-11-28 18:58:55 -05:00
..
CMakeLists.txt
ConnectionFromClient.cpp
ConnectionFromClient.h
ConsoleGlobalEnvironmentExtensions.cpp
ConsoleGlobalEnvironmentExtensions.h
Documentation.txt
Forward.h
ImageCodecPluginSerenity.cpp
ImageCodecPluginSerenity.h
main.cpp
PageClient.cpp
PageClient.h
PageHost.cpp
PageHost.h
WebContentClient.ipc
WebContentConsoleClient.cpp
WebContentConsoleClient.h
WebContentServer.ipc
WebDriverClient.ipc
WebDriverConnection.cpp
WebDriverConnection.h
WebDriverServer.ipc