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

We had some discussion of this in [today's TAG meeting](https://github.com/w3ctag/meetings/blob/gh-pages/2017/telcons/07-05-agenda.md) in order to assign the issue.  Two themes came up:
* how much variation between implementations there is in when decoding happens, and whether this restricts things current implementations do or whether the API makes assumptions about certain implementation strategies that might not match all implementations (or encourages developers to make such assumptions)
  * it seems at first glance like it may mostly be good, although I'm a little worried about the requirement that *all* frames of an animated image be decoded, given that it seems like something that implementations may well want to optimize for large animated images in low-ish memory situations
* how this ties to the [Extensible Web Manifesto](https://extensiblewebmanifesto.org/), and whether it helps to explain `<img>` or whether it could be done differently in a way that does

-- 
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-313151823