ladybird/Libraries/LibWeb/Worker/WebWorkerClient.ipc

#include <LibURL/URL.h>
#include <LibWeb/Cookie/Cookie.h>

endpoint WebWorkerClient {
    did_close_worker() =|
    did_request_cookie(URL::URL url, Web::Cookie::Source source) => (String cookie)
}
LibWeb: Implement cookie fetching for Workers Allows formulas to update on Google Sheets, which uses a Worker to update them and makes cookie authenticated requests, which was failing before this commit. This has the limitation that it has to proxy through the WebContent process, but that's how the current infrastructure is, which is outside the scope of this commit. 2025-09-07 15:32:43 +01:00			`#include <LibURL/URL.h>`
			`#include <LibWeb/Cookie/Cookie.h>`

LibWeb+WebWorker: Move worker execution into a new WebWorker process We now create a WorkerAgent for the parent context, which is currently only a Window. Note that Workers can have Workers per the spec. The WorkerAgent spawns a WebWorker process to hold the actual script execution of the Worker. This is modeled with the DedicatedWorkerHost object in the WebWorker process. A start_dedicated_worker IPC method in the WebWorker IPC creates the WorkerHost object. Future different worker types may use different IPC messages to create their WorkerHost instance. This implementation cannot yet postMessage between the parent and the child processes. Co-Authored-By: Andreas Kling <kling@serenityos.org> 2023-11-08 11:47:41 -07:00			`endpoint WebWorkerClient {`
LibWeb+WebWorker: Add IPC messages to request and communicate shutdown 2024-07-09 03:00:06 -06:00			`did_close_worker() =\|`
LibWeb: Implement cookie fetching for Workers Allows formulas to update on Google Sheets, which uses a Worker to update them and makes cookie authenticated requests, which was failing before this commit. This has the limitation that it has to proxy through the WebContent process, but that's how the current infrastructure is, which is outside the scope of this commit. 2025-09-07 15:32:43 +01:00			`did_request_cookie(URL::URL url, Web::Cookie::Source source) => (String cookie)`
LibWeb+WebWorker: Move worker execution into a new WebWorker process We now create a WorkerAgent for the parent context, which is currently only a Window. Note that Workers can have Workers per the spec. The WorkerAgent spawns a WebWorker process to hold the actual script execution of the Worker. This is modeled with the DedicatedWorkerHost object in the WebWorker process. A start_dedicated_worker IPC method in the WebWorker IPC creates the WorkerHost object. Future different worker types may use different IPC messages to create their WorkerHost instance. This implementation cannot yet postMessage between the parent and the child processes. Co-Authored-By: Andreas Kling <kling@serenityos.org> 2023-11-08 11:47:41 -07:00			`}`