-
-
Notifications
You must be signed in to change notification settings - Fork 582
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
Sidebar (for tabs) with different sizes for elements whille expanding #3040
Comments
I found related discussions and issues that might be helpful:
|
I liked the idea of using expand-on-hover but find it currently unusable due to the layout shift. Here is an idea for solving it: When expand on hover is enabled:
|
@quxer Why is this not getting enough attention? |
I don't know. But probably with beta release and disabling expand on hover, this issue will be pushed down the line or forgotten. |
Hi, @quxer. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
Captchas
What happened?
When sidebar is set to collapsed mode with expanding on hover there are problems with button sizes.
With workspaces, while expanded workspace button has smaller hight, which causes all tabs to be shifted upwards. With many tabs it is so distracting and hard to click on the one you want. Profile button is shifted a little as well.
When I disable workspaces, then tabs while expading are shifted downwards. While collapsed profile button with separator are too high and go downwards too.
I tried reseting to default buttons placement, but it was worse with more buttons next to profile button. To add to that this shifting behaviour is from many versions ago, many from the start. Once it was almost fixed, but with new changes to placement of buttons it's got worse. It is almost like both versions of sidebar are different elements between which we are switching.
Reproducible?
Version
1.0.1-a.19
What platform are you seeing the problem on?
Windows
Relevant log output
No response
The text was updated successfully, but these errors were encountered: