Re: [w3ctag/design-reviews] Request to review Image Decode API (#182)

Quoting https://github.com/w3ctag/design-reviews/issues/182#issuecomment-313245241 :
> For the animated case, the requirement is that the frames are available but not necessarily that they need be decoded. That is, essentially "onload" has to fire and then the first frame of the animated image is decoded before the callback is issued. Calling this API does not require that every frame needs to be decoded, for the reasons that you mention (it may not feasible in low memory situations).

Where does the spec say this?  To me, the current spec text seems to say the opposite, since it says:
> Decode the image's media data entirely into its bitmap form, suitable for rapid painting to the screen.

and I don't see any exceptions for only decoding the first (or current?) frame of the animated image.

Also, is it possible for the current frame of an animated image to change between the call to decode() and the "end of the next update the rendering step in the event loop"?  If so, which frame should be guaranteed to be decoded?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/182#issuecomment-313247696

Received on Wednesday, 5 July 2017 22:48:32 UTC