refactor: improve image embedding and async image loading #504
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug fix and Refactor
updateHTMLImageElement
andupdateSVGImageElement
helper functions with proper JSDoc comments.options.onImageErrorHandler
and ensuring lazy-loaded images are set to eager.svgToDataURL
andnodeToDataURL
to verify correct data URL conversion.These changes improve code clarity, reliability, and performance in the image embedding process.
Description
Motivation and Context
This change leverages the native
decode()
method on image elements to ensure that images are fully processed before rendering. Previously, we encountered issues where the final rendered output was incomplete or inconsistent because the image data hadn't been fully decoded when the source was assigned. By invokingdecode()
, we:decode()
follows modern web standards for asynchronous image processing, as detailed in the MDN documentation.This change started because I was reading these issues, and decided to find the root cause of an issue on my project:
Types of changes
Self Check before Merge