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

Bug: Service labels cut off when using Slim Sidebar #232

Closed
1 task done
HenrijsS opened this issue Jun 11, 2022 · 0 comments · Fixed by #245
Closed
1 task done

Bug: Service labels cut off when using Slim Sidebar #232

HenrijsS opened this issue Jun 11, 2022 · 0 comments · Fixed by #245
Labels
bug 🪲 Something isn't working

Comments

@HenrijsS
Copy link

Avoid duplicates

  • I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0-nightly.56

What Operating System are you using?

Windows

Operating System Version

Windows 11 Home Version 21H2

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

Fully visible Service names

Actual Behavior

The height of the Service square is too short and the overflow hides the Service name specifically when using "SLIM" Sidebar

Steps to reproduce

  1. Go to settings
  2. Select the Appearance tab
  3. Scroll to Sidebar settings
  4. Set Sidebar Width to Slim sidebar
  5. See that services on the left have their names cut off. (If enabled).

Debug link

https://debug.ferdium.org/0b668f89-3a1b-44d5-a11b-976780adf44a

Screenshots

image
image

Additional information

It also seems like that the height is not correct on a Normal sidebar.

You can see that the content overlaps the Padding:
image

@HenrijsS HenrijsS added the bug 🪲 Something isn't working label Jun 11, 2022
SpecialAro added a commit to SpecialAro/ferdium-app that referenced this issue Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant