yall.js: Uncaught (in promise) DOMException: The source image cannot be decoded.

Uncaught (in promise) DOMException: The source image cannot be decoded. Any idea why? It works for other images.

Thank you for making this JavaScript script. I am using the yall-2.0.1.min.js file.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 19 (11 by maintainers)

Commits related to this issue

2.2.0 release - Added linting via eslint. - Updated Babel to version 7. - Added @babel/preset-env. May add a separate leaner build for mjs in the future. - Resolved bugs #24 and #28 by removing async ... — committed to malchata/yall.js by malchata 6 years ago

Most upvoted comments

Thank you for merging that in.

I think you are right about removing image decode. I saw this: “Decoding of large images can block the main thread for hundreds of milliseconds or more, interrupting fluid animations and user interaction. Currently, there’s no way for a web author to specify that they want an image to be decoded asynchronously, so there are scenarios where it is impossible to avoid UI stalls.” https://github.com/whatwg/html/issues/1920

SHerms on Oct 29, 2018

I’m sorry you’re having this kind of trouble. It’s starting to make me wonder if async decoding is worth the trouble. 🤕

If at any point you could share the code, let me know. I haven’t received this error, but just because no one else has said anything doesn’t make me think this isn’t a potential problem.

I’ll keep this issue open for the foreseeable future in case anyone else is having trouble. In the meantime, try this unofficial build which removes async image decoding: yall-2.0.3.min.js.zip

Best of luck!

malchata on Aug 3, 2018

Can you provide the image (or image set) that ran into decoding issues? Do you have an example of this in the wild, currently?

Thanks for raising this!

Also, please be aware that 2.0.1 is not a supported release yet. 😃 2.0.0 is the latest official release over on the releases page.

malchata on Jul 31, 2018