[release/10.0-preview4] [browser] Ensure compression targets run after preloading #114960
Conversation
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
|
Tagging subscribers to 'arch-wasm': @lewing |
javiercn
approved these changes
Apr 23, 2025
Open
3 tasks
|
Ping me when it's approved by Tactics and ready to merge. |
lewing
approved these changes
Apr 24, 2025
1e69c98
into
dotnet:release/10.0-preview4
31 of 33 checks passed
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.
Backport of #114953
Backport of #114940 to release/10.0-preview4
Customer Impact
Customers using WebAssembly preloading (on by default) loses the ability to use pre-compressed asset endpoint for preloaded asset in Blazor Web scenario.
Regression
Preloading is a new feature, but it is on by default.
Risk
Low. Manually tested on failing cases in SDK repository.