ladybird/Services/WebContent/WebContentClient.ipc

endpoint WebContentClient = 90
{
    DidFinishLoad(URL url) =|
    DidPaint(Gfx::IntRect content_rect, i32 shbuf_id) =|
    DidInvalidateContentRect(Gfx::IntRect content_rect) =|
    DidChangeSelection() =|
}
WebContent: Start work on browser process separation :^) The "WebContent" service provides a very restricted instance of LibWeb running as an unprivileged user account. This will be used to implement process separation in Browser, among other things. This first cut of the service only spawns a single WebContent process when someone connects to /tmp/portal/webcontent. We will soon switch this over to spawning a new process for each connection. Since this feature is very immature, we'll be bringing it up inside of Demos/WebView as a separate demo program. Eventually this will become a reusable widget that anyone can embed and easily get out-of-process web content in their GUI. This is pretty, pretty cool! :^) 2020-06-17 17:31:42 +02:00			`endpoint WebContentClient = 90`
			`{`
			`DidFinishLoad(URL url) =\|`
			`DidPaint(Gfx::IntRect content_rect, i32 shbuf_id) =\|`
WebContent: Allow the WebContent process to trigger repaints After layout, we may want to repaint the page, so we now listen for the PageClient::page_did_invalidate() notification and use it to drive a client-side repaint. Note that an invalidation request from LibWeb makes a full roundtrip to the WebContent client and back since the client drives painting. 2020-06-17 18:00:18 +02:00			`DidInvalidateContentRect(Gfx::IntRect content_rect) =\|`
WebContent: Notify client when web content selection changes The WebContentView widgets reacts to this by requesting a repaint. 2020-07-04 20:57:57 +02:00			`DidChangeSelection() =\|`
WebContent: Start work on browser process separation :^) The "WebContent" service provides a very restricted instance of LibWeb running as an unprivileged user account. This will be used to implement process separation in Browser, among other things. This first cut of the service only spawns a single WebContent process when someone connects to /tmp/portal/webcontent. We will soon switch this over to spawning a new process for each connection. Since this feature is very immature, we'll be bringing it up inside of Demos/WebView as a separate demo program. Eventually this will become a reusable widget that anyone can embed and easily get out-of-process web content in their GUI. This is pretty, pretty cool! :^) 2020-06-17 17:31:42 +02:00			`}`