Larger Extension Editor preview

[WebMechanic]

The extension preview features a very space wasting side panel that contains very little information given the space it occupies and could easily fit to the right side of the header. This would leave much more room to the IFrame rendering the extension's readme/description which often is too narrow -- for people not having a HD/Retina monitor, a monitor under 2K (i.e me) or with screen scaling enabled. So consider this an a11y feature as well.

Here's a simple mock-up of how this could look like instead:

The header being a flex container would then have three flex children. The following flex values seemed reasonable when I tried this in the dev-tools:
.icon-container: flex:1
.details: flex: 4
.additional-details-container: flex: 1 (the new one, originally from the right side of .content)

Then .content > .details would no longer require to be a flex container for the lack of useful child elements. It appears .readme-container's only purpose was to move the sidebar to the right.

Thanks for considering.

[WebMechanic]

oh, and please allow ALL SCROLLBARS in the GUI to be changed to scrollbar-width: auto; because the thin version is a nuisance and hard to hit. A hateworthy fad that also makes many websites hard to use.

Not everyone uses a touch screen or mouse with a scroll wheel => a11y request 2

Thank you! 🙏🏻

[vscode-triage-bot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscode-triage-bot]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscode-triage-bot]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!