ladybird/Libraries/LibWeb/WebGL/WebGLSync.h
Aliaksandr Kalenik a80babffb6 LibWeb+Compositor: Run canvas contexts in the Compositor
Canvas rendering is a major remaining path where WebContent directly
owns GPU-facing drawing state. Back 2D and WebGL canvas contexts with
remote Compositor transports, so WebContent talks to canvas surfaces
through IPC while the Compositor owns the rasterization resources.

This is a large step toward GPU sandboxing because canvas GPU work now
lives behind the Compositor boundary. It also gives OffscreenCanvas the
process-independent canvas plumbing that HTMLCanvasElement now uses,
making worker-owned canvases possible without another WebContent-local
rendering path.
2026-06-17 19:07:32 +02:00

34 lines
912 B
C++

/*
* Copyright (c) 2024, Andrew Kaster <andrew@ladybird.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
#include <LibWeb/WebGL/Types.h>
#include <LibWeb/WebGL/WebGLObject.h>
namespace Web::WebGL {
class WebGLSync : public WebGLObject {
WEB_PLATFORM_OBJECT(WebGLSync, WebGLObject);
GC_DECLARE_ALLOCATOR(WebGLSync);
public:
static GC::Ref<WebGLSync> create(JS::Realm& realm, GC::Ref<WebGLRenderingContextBase>, GLsyncInternal handle);
virtual ~WebGLSync() override;
ErrorOr<GLsyncInternal> sync_handle(WebGLRenderingContextBase const* context) const;
ErrorOr<Optional<GLsyncInternal>> sync_handle_for_deletion(WebGLRenderingContextBase const* context);
protected:
explicit WebGLSync(JS::Realm&, GC::Ref<WebGLRenderingContextBase>, GLsyncInternal handle);
virtual void initialize(JS::Realm&) override;
GLsyncInternal m_sync_handle { nullptr };
};
}