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

As a curious question, it seems like there are two modes here being proposed - sync and async - since there is a mechanism that allows an explicit request to decode a certain HTMLImageElement, I'm curious if there should be a "no decode" mode (to save memory, and potentially VRAM in certain cases) for resources that the content developer only would like to have available given that the user triggers a specific view where this image needs to be shown. With decode() (which from what I see has had some debates on whether or not it is the best name, setting that discussion aside) it seems like this would allow placeholding image elements and only decoding them when deemed needed.

As for what has been proposed, I'll have to wait for @dbaron 's feedback on this since he is the assigned reviewer for this.

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