Bug 170037

Summary: [CG] The animated image doesn't need to cache the current frame after drawing it
Product: WebKit Reporter: Said Abou-Hallawa <sabouhallawa>
Component: ImagesAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: simon.fraser, thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

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>