Re: [w3ctag/design-reviews] Img decoding attribute (#220)

This was brought up during the London F2F - we understand the underlying problem this is attempting to address, and believe we are in agreement on the importance giving better control on when and how images are decoded in a document.

That said, we have spent a reasonable time of this during the F2F at great length, and have some concerns on the approach taken here. The approach taken here seems to be intended to address the problem in limited scope for simplicity, where we could be trying to address this in a more extensible way - exposing the primitives surrounding loading, decoding, and eventually rasterizing images in a way that provides the building blocks for developers to define the behavior as they see fit.

The comments above cover the property discussed in this review, but also the `decode()` API which we have recently done a review on.

-- 
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/220#issuecomment-362635384