Images 💾⌗

Last commit ⭐⌗ 

commit 02936f694422c1d4732cfcf4aadb30fc126e224d
Author:     Aliaksandr Kalenik <kalenik.aliaksandr@gmail.com>
AuthorDate: Thu Dec 21 22:58:54 2023 +0100
Commit:     Andreas Kling <kling@serenityos.org>
CommitDate: Fri Dec 22 17:47:34 2023 +0100

    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.