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: sbb-usermenu cuts long names #172

Closed
jeripeierSBB opened this issue Sep 16, 2019 · 0 comments · Fixed by #232
Closed

Bug: sbb-usermenu cuts long names #172

jeripeierSBB opened this issue Sep 16, 2019 · 0 comments · Fixed by #232
Labels
bug Something isn't working comp: lean Issues related to @sbb-esta/angular lean design comp: standard Issues related to @sbb-esta/angular standard design effort1: hours prio3: medium Should be done when time available

Comments

@jeripeierSBB
Copy link
Collaborator

Describe the bug
If there is an user with a long name, the displayName is cut, when the underlaying dropdown is open.

To Reproduce
Steps to reproduce the behavior:

  1. Use sbb-username with a long displayName
  2. See cut name

Expected behavior
Wider element (as if dropdown is not open), or cut name and use "..."

Screenshots
image

Desktop (please complete the following information):

  • OS: windows
  • Browser: chrome
@jeripeierSBB jeripeierSBB added the bug Something isn't working label Sep 16, 2019
@kyubisation kyubisation added comp: lean Issues related to @sbb-esta/angular lean design comp: standard Issues related to @sbb-esta/angular standard design effort1: hours prio3: medium Should be done when time available labels Sep 17, 2019
kyubisation pushed a commit that referenced this issue Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working comp: lean Issues related to @sbb-esta/angular lean design comp: standard Issues related to @sbb-esta/angular standard design effort1: hours prio3: medium Should be done when time available
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants