-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release #1908
Conversation
* fix: image element rendering triggers an exception * chore: add image bugfix demo #1906
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
WalkthroughThis pull request introduces several changes across multiple packages, primarily focusing on updating dependencies and fixing issues related to image rendering. It includes changes to ESLint configurations, test cases for bug fixes, and updates to changelogs and package.json files for various packages. Changes
|
|
||
// remove && expect no error | ||
requestAnimationFrame(() => { | ||
image.remove(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The variable image
is used before it is defined. This will lead to a runtime error. Consider defining image
before using it in the requestAnimationFrame
callback.
@@ -244,7 +254,9 @@ export class ImageRenderer extends DefaultRenderer { | |||
imageRect, | |||
drawRect, | |||
}); | |||
} catch {} | |||
} catch { | |||
// expected error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Catching an empty block without handling or logging the error might lead to silent failures. Consider logging the error or handling it appropriately to avoid missing critical issues.
No description provided.