[Webkit-unassigned] [Bug 170037] New: [CG] The animated image does need to cache the current frame after drawing it

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=170037

            Bug ID: 170037
           Summary: [CG] The animated image does need to cache the current
                    frame after drawing it
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Images
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sabouhallawa at apple.com

For animated images, WebKit needs the current frame only to be cached. Since the frames of an animated image are drawn in order, CG has to cache the current frame anyway. By applying the frame diff to the current frame, CG can generate the next frame. So after drawing the current frame of an animated image, WebKit does not need to cache it because it is already cached by CG.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170323/183f3c53/attachment-0001.html>