Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extensions page should default to closed expanders #2106

Closed
cinnamon-msft opened this issue Jan 5, 2024 · 0 comments · Fixed by #2107
Closed

Extensions page should default to closed expanders #2106

cinnamon-msft opened this issue Jan 5, 2024 · 0 comments · Fixed by #2107
Labels
Area-Extensibility Related to extensions Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Issue-Task Feature request that doesn't need a major design Resolution-Fix-Available Available in a release

Comments

@cinnamon-msft
Copy link
Contributor

Suggested new feature or improvement

I have a lot of extensions installed and the page launches with all of the extension expanders opened, displaying "Manage extension" for each of them. We should have the default behavior for this page be closed expanders.

Scenario

People with a lot of extensions will have to scroll and visually parse which extension they're looking for, which isn't ideal.

Additional details

No response

@cinnamon-msft cinnamon-msft added the Issue-Feature New feature or request label Jan 5, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Jan 5, 2024
@cinnamon-msft cinnamon-msft added Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Area-Extensibility Related to extensions Issue-Task Feature request that doesn't need a major design and removed Issue-Feature New feature or request Needs-Triage New issue that the core contributors need to triage labels Jan 5, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Jan 6, 2024
@krschau krschau added this to the Dev Home v0.10 milestone Jan 10, 2024
@krschau krschau added Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release and removed In-PR This issue has a related PR labels Jan 11, 2024
@krschau krschau added Resolution-Fix-Available Available in a release and removed Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release labels Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Extensibility Related to extensions Good-First-Issue Good for newcomers Help-Wanted We encourage anyone to jump in on these Issue-Task Feature request that doesn't need a major design Resolution-Fix-Available Available in a release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants