You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I want to conveniently work with the left toolbar also if it contains many views that go beyond what can be shown in the available space.
Currently Theia shows a scroll bar, if the number of views in the left toolbar go beyond what can be shown in the available space, whereas the scrollbar only becomes visible when users hover over the toolbar. This is not very intuitive.
A behavior similar to VS Code would be more user friendly. Instead of displaying a scroll bar a new icon showing three dots should appear as the last item in the toolbar if there are more views than can currently fit in.
On clicking the three dots, a menu showing all views that aren’t visible shall be displayed.
The toolbar with the three dots at the end should always show the following:
Views that fit on the screen
The currently active view
The three dots
If the currently active view would not fit at the moment, it becomes the last item after the views that still fit and before the three dots. If the currently active view fits on the list of visible views, it remains at the original position and is shown as active.
In our opinion this is major UX improvement compared to the way it is currently handled and should be implemented as the default behavior. However, if the community disagrees we can also aim at making this an opt-in feature that is configurable via preferences.
The text was updated successfully, but these errors were encountered:
@tortmayr This feature would also be great for the menu bar, since we don't even have a scrollbar there. Menus just move into the invisible area of the document.
Rework behavior of the sidepanels if there more tabs than they can fit.
Introduce behavior similar to VS Code: Overflowing tabs will simply be hidden or 'merged' into one menu button at the end
of the tabbar. Clicking the button allows revealing of a currently hidden view.
Special handling is implemented to ensure that the currently selected view never gets hidden away.
Fixes#12416
Rework behavior of the sidepanels if there more tabs than they can fit.
Introduce behavior similar to VS Code: Overflowing tabs will simply be hidden or 'merged' into one menu button at the end
of the tabbar. Clicking the button allows revealing of a currently hidden view.
Special handling is implemented to ensure that the currently selected view never gets hidden away.
Fixes#12416
Rework behavior of the sidepanels if there more tabs than they can fit.
Introduce behavior similar to VS Code: Overflowing tabs will simply be hidden or 'merged' into one menu button at the end
of the tabbar. Clicking the button allows revealing of a currently hidden view.
Special handling is implemented to ensure that the currently selected view never gets hidden away.
Contributed on behalf of STMicroelectronics
Fixes#12416
As a user, I want to conveniently work with the left toolbar also if it contains many views that go beyond what can be shown in the available space.
Currently Theia shows a scroll bar, if the number of views in the left toolbar go beyond what can be shown in the available space, whereas the scrollbar only becomes visible when users hover over the toolbar. This is not very intuitive.
A behavior similar to VS Code would be more user friendly. Instead of displaying a scroll bar a new icon showing three dots should appear as the last item in the toolbar if there are more views than can currently fit in.
On clicking the three dots, a menu showing all views that aren’t visible shall be displayed.
The toolbar with the three dots at the end should always show the following:
If the currently active view would not fit at the moment, it becomes the last item after the views that still fit and before the three dots. If the currently active view fits on the list of visible views, it remains at the original position and is shown as active.
In our opinion this is major UX improvement compared to the way it is currently handled and should be implemented as the default behavior. However, if the community disagrees we can also aim at making this an opt-in feature that is configurable via preferences.
The text was updated successfully, but these errors were encountered: