Repository navigation
Fixes WASM browser file picker crashing while listing entries of folders - #21449
Merged
Merged
Conversation
Contributor
Author
|
Linked issue was caused by removing the version pin here 09fefed#diff-29283bdd3594ef891fe6e0036ad8c8fe8e984d37b9486061a9bf6283b526fa25 |
maxkatz6
approved these changes
May 28, 2026
maxkatz6
enabled auto-merge
May 28, 2026 22:08
maxkatz6
added this pull request to the merge queue
Jun 3, 2026
|
You can test this PR using the following package version. |
MrJul
added a commit
to MrJul/Avalonia
that referenced
this pull request
Jun 23, 2026
Co-authored-by: Julien Lebosquain
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.
What does the pull request do?
Pins the version for wasm native file system dependency, avoiding the crash that can occur on Chromium browsers when listing entries in a StorageFolderItem.
What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues
Fixes #21145