Bug 170037 - [CG] The animated image doesn't need to cache the current frame after drawing it
Summary: [CG] The animated image doesn't need to cache the current frame after drawing it
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Images (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2017-03-23 16:50 PDT by Said Abou-Hallawa
Modified: 2017-03-23 19:01 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Said Abou-Hallawa 2017-03-23 16:50:35 PDT
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.
Comment 1 Radar WebKit Bug Importer 2017-03-23 16:58:56 PDT
<rdar://problem/31231750>