ladybird/Userland/Services/WebContent/WebDriverServer.ipc

#include <LibWeb/WebDriver/Response.h>

endpoint WebDriverServer {
    navigation_complete(Web::WebDriver::Response response) =|
    window_rect_updated(Web::WebDriver::Response response) =|
    find_elements_complete(Web::WebDriver::Response response) =|
    script_executed(Web::WebDriver::Response response) =|
    actions_performed(Web::WebDriver::Response response) =|
    dialog_closed(Web::WebDriver::Response response) =|
    screenshot_taken(Web::WebDriver::Response response) =|
}
WebDriver: Handle script execution results without spinning event loops We currently spin the platform event loop while awaiting scripts to complete. This causes WebContent to hang if another component is also spinning the event loop. The particular example that instigated this patch was the navigable's navigation loop (which spins until the fetch process is complete), triggered by a form submission to an iframe. So instead of spinning, we now return immediately from the script executors, after setting up listeners for either the script's promise to be resolved or for a timeout. The HTTP request to WebDriver must finish synchronously though, so now the WebDriver process spins its event loop until WebContent signals that the script completed. This should be ok - the WebDriver process isn't expected to be doing anything else in the meantime. Also, as a consequence of these changes, we now actually handle time outs. We were previously creating the timeout timer, but not starting it. 2024-09-13 07:42:24 -04:00			`#include <LibWeb/WebDriver/Response.h>`

WebContent: Add a very-empty WebDriver IPC class to WebContent This just sets up the infrastructure for the WebContent process to house WebDriver IPCs, and adds an IPC for WebContent to create the WebDriver connection. The WebDriverConnection class inside WebContent ultimately will contain most of what is currently in WebDriver::Session (so the copyright attributions are copied here as well). The socket created by WebDriver is currently /tmp/browser_webdriver (formatted with some IDs). This will be moved to the /tmp/webdriver folder, as WebDriver will create multiple sockets to communicate with both Browser and WebContent as the IPCs are iteratively moved to WebContent. That path is unveiled here, though it is unused as of this commit. 2022-11-08 10:03:07 -05:00			`endpoint WebDriverServer {`
WebContent+WebDriver: Asynchronously wait for navigations to complete Similar to commit c2cf65adac78912883996153fb608dafe389b6e0, we should avoid spinning the event loop from the WebContent-side of the WebDriver connection. This can result in deadlocks if another component in LibWeb also spins the event loop. The AO to await navigations has two event loop spinners - waiting for the navigation to complete and for the document to reach the target readiness state. We now use NavigationObserver and DocumentObserver to be notified when these conditions are met. And we use the same async IPC mechanism as script execution to notify the WebDriver process when all conditions are met (or timed out). 2024-10-25 10:28:29 -04:00			`navigation_complete(Web::WebDriver::Response response) =\|`
LibWeb+WebContent+WebDriver+UI: Make window rect updates asynchronous It's currently possible for window size/position updates to hang, as the underlying IPCs are synchronous. This updates the WebDriver endpoint to be async, to unblock the WebContent process while the update is ongoing. The UI process is now responsible for informing WebContent when the update is complete. 2024-10-28 23:37:11 -04:00			`window_rect_updated(Web::WebDriver::Response response) =\|`
WebContent+WebDriver: Make the element locator endpoints asynchronous We currently spin the event loop to wait for the specified element to become available. As we've seen with other endpoints, this can result in dead locks if another web component also spins the event loop. This patch makes the locator implementations asynchronous. 2024-10-30 15:26:04 -04:00			`find_elements_complete(Web::WebDriver::Response response) =\|`
WebDriver: Handle script execution results without spinning event loops We currently spin the platform event loop while awaiting scripts to complete. This causes WebContent to hang if another component is also spinning the event loop. The particular example that instigated this patch was the navigable's navigation loop (which spins until the fetch process is complete), triggered by a form submission to an iframe. So instead of spinning, we now return immediately from the script executors, after setting up listeners for either the script's promise to be resolved or for a timeout. The HTTP request to WebDriver must finish synchronously though, so now the WebDriver process spins its event loop until WebContent signals that the script completed. This should be ok - the WebDriver process isn't expected to be doing anything else in the meantime. Also, as a consequence of these changes, we now actually handle time outs. We were previously creating the timeout timer, but not starting it. 2024-09-13 07:42:24 -04:00			`script_executed(Web::WebDriver::Response response) =\|`
LibWeb+WebContent+WebDriver: Implement the Perform Actions endpoint Similar to script execution, this spins the WebDriver process until the action is complete (rather than spinning the WebContent process, which we've seen result in deadlocks). 2024-09-29 09:40:17 -04:00			`actions_performed(Web::WebDriver::Response response) =\|`
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. 2024-10-25 12:31:07 -04:00			`dialog_closed(Web::WebDriver::Response response) =\|`
LibWeb+WebContent+WebDriver: Make the screenshot endpoints asynchronous These were the last WebDriver endpoints spinning the event loop. 2024-10-30 20:29:26 -04:00			`screenshot_taken(Web::WebDriver::Response response) =\|`
WebContent: Add a very-empty WebDriver IPC class to WebContent This just sets up the infrastructure for the WebContent process to house WebDriver IPCs, and adds an IPC for WebContent to create the WebDriver connection. The WebDriverConnection class inside WebContent ultimately will contain most of what is currently in WebDriver::Session (so the copyright attributions are copied here as well). The socket created by WebDriver is currently /tmp/browser_webdriver (formatted with some IDs). This will be moved to the /tmp/webdriver folder, as WebDriver will create multiple sockets to communicate with both Browser and WebContent as the IPCs are iteratively moved to WebContent. That path is unveiled here, though it is unused as of this commit. 2022-11-08 10:03:07 -05:00			`}`