ladybird/Services/WebContent
Andreas Kling 0bac2ad3b3 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 20:09:44 +02:00
..
ClientConnection.cpp WebContent: Allow the WebContent process to trigger repaints 2020-06-17 20:09:44 +02:00
ClientConnection.h WebContent: Start work on browser process separation :^) 2020-06-17 20:09:44 +02:00
CMakeLists.txt WebContent: Start work on browser process separation :^) 2020-06-17 20:09:44 +02:00
Forward.h WebContent: Start work on browser process separation :^) 2020-06-17 20:09:44 +02:00
main.cpp WebContent: Start work on browser process separation :^) 2020-06-17 20:09:44 +02:00
PageHost.cpp WebContent: Allow the WebContent process to trigger repaints 2020-06-17 20:09:44 +02:00
PageHost.h WebContent: Allow the WebContent process to trigger repaints 2020-06-17 20:09:44 +02:00
WebContentClient.ipc WebContent: Allow the WebContent process to trigger repaints 2020-06-17 20:09:44 +02:00
WebContentServer.ipc WebContent: Start work on browser process separation :^) 2020-06-17 20:09:44 +02:00