Extensions page expanders behavior is set to closed by default #2107
Conversation
This file contains 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
krschau
approved these changes
Jan 6, 2024
dkbennett
approved these changes
Jan 10, 2024
|
Thank you a lot for approval! |
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.
Summary of the pull request
The pull request makes changes to the ExtensionLibraryView.xaml for the expanders to be closed by default, as was proposed by cinnamon-msft Issue #2106
References and relevant issues
Closes #2106
Detailed description of the pull request / Additional comments
Expanders' behavior is set to be closed by default, so the people with a lot of extensions will have not to scroll and visually parse which extension they're looking for.