mirror of
https://github.com/RGBCube/serenity
synced 2025-05-14 09:24:57 +00:00
LibWebView+WebContent: Drive repainting from WebContent process
With this change, chrome no longer has to ask the WebContent process to paint the next frame into a specified bitmap. Instead, it allocates bitmaps and sends them to WebContent, which then lets chrome know when the painting is done. This work is a preparation to move the execution of painting commands into a separate thread. Now, it is much easier to start working on the next frame while the current one is still rendering. This is because WebContent does not have to inform chrome that the current frame is ready before it can request the next frame. Additionally, as a side bonus, we can now eliminate the did_invalidate_content_rect and did_change_selection IPC calls. These were used solely for the purpose of informing chrome that it needed to request a repaint.
This commit is contained in:
parent
ac63d1e59d
commit
02936f6944
17 changed files with 68 additions and 152 deletions
|
@ -35,8 +35,6 @@ private:
|
|||
virtual void did_request_navigate_back() override;
|
||||
virtual void did_request_navigate_forward() override;
|
||||
virtual void did_request_refresh() override;
|
||||
virtual void did_invalidate_content_rect(Gfx::IntRect const&) override;
|
||||
virtual void did_change_selection() override;
|
||||
virtual void did_request_cursor_change(i32) override;
|
||||
virtual void did_layout(Gfx::IntSize) override;
|
||||
virtual void did_change_title(ByteString const&) override;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue