IJSRuntimeExtensions: Fix when pre-rendering #10142
Merged
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: #10141
Regression from: #9997
Apparently, there are are two
JSRuntimetypes that throw similar error:UnsupportedJavaScriptRuntimeduring static SSR.RemoteJSRuntime- during SSR pre-render.In the #9997 I removed when it was just checking for word "prerending" in the exception message and went for checking the JS runtime type instead.
The
IsJsInteropAvailabledoesn't help here, as it happening not on a component level, but during pre-render the DI is disposing the whole container, theBrowserViewportServiceis part of it, and it invokesDisposeAsyncthat has a JS call, so there is nothing better than just ignore this errors.How Has This Been Tested?
Manually + bUnit test
Type of Changes
Checklist
dev).