MudThemeProvider: Wrap JS in a try-catch#9042
Merged
ScarletKuro merged 1 commit intoMudBlazor:devfrom May 23, 2024
Merged
Conversation
github-actions
bot
added
bug
ScarletKuro
changed the title
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
1 participant
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.
Description
Fixes: #8991
It's questionable whether it fixes it completely, since the DOM is modified and Blazor doesn't like this. However, we wrap most of our JS calls in
InvokeAsyncWithErrorHandling, and as I mentioned in the comment, there is nothing else we can do.Feel free to ask if you need further assistance!
How Has This Been Tested?
None
Type of Changes
Checklist
dev).