-
Notifications
You must be signed in to change notification settings - Fork 32.6k
Allow settings UI TOC to be resized #79581
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
Comments
@dalongi a probably-simple workaround might be to add the full name of the category as a hover tip for the truncated text. |
I don't really want to make things wider by default right now but a fancier UI would let you resize the TOC to your preference. I will add a tooltip now, should have had that already. |
@roblourens: Would additionally adding the resize UI be nontrivial? I'm not familiar with the UX framework being used, but could look into sending a PR if it's not too bad or there is an example to look at. For changing the width: do you know how wide people typically have these panes? (Is it full window or partial due to having multiple editors?) When I have it open as the only window, I find it's easier to read the right-side setting descriptions when I shrink the window (~60-80 char per line instead of ~135 at max width) |
Yeah I think it would be nontrivial. I would think that people usually use this full-window but I don't have a good sense of the average window width. |
+1 to this. Our team has two extensions "Azure Machine Learning" and "Azure Machine Learning - Remote" that show up in the TOC as: Users have to click through each of those options to get to the right extension. We purposely added "Remote" as a suffix so that both the main and remote extensions would be grouped together, as the list is sorted alphabetically today. Would it be possible for users to expand the column width so they can see the full extension name? |
The TOC in settings is rather narrow, and frequently truncates extension names. This feels especially unnecessary when using a wider display.

This is not only triggered by extension names, but also affects built-in settings in non-English languages:

Ideas:
The text was updated successfully, but these errors were encountered: