Merged
Conversation
Co-authored-by: erik <erik@zettersten.com>
|
Cursor Agent can help with this pull request. Just |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sanitize non-finite numeric arguments for canvas gradient creation methods in JS to prevent
JSExceptioncrashes.The Blazor demo was crashing due to
Microsoft.JSInterop.JSException: Failed to execute 'createLinearGradient' on 'CanvasRenderingContext2D': The provided double value is non-finite.This occurred whenNaNorInfinityvalues were passed from .NET to JavaScript for gradient coordinates, causing the browser's canvas API to throw an error and halt the render loop. This fix coerces such non-finite numbers to0before invoking the canvas API.