2865: Long group names break the dashboard view

ste****@gmai***** (Google Code) (Is this you? Claim this profile.)
Sept. 20, 2013 
What version are you running?
1.6.14

What's the URL of the page containing the problem?
"/dashboard/"

What steps will reproduce the problem?
1. Be part of a team with a long name (e.g. Meta_Syntactic_Variable_Names)
2. Navigate to the dashboard

What is the expected output? What do you see instead?
I expect to see a sidebar and dashboard, as usual. Instead the main dashboard overlaps the sidebar and is positioned below the last element in the sidebar. For someone who is in many teams this can put the main dashboard element below the fold (not pictured here).

What operating system are you using? What browser?
E.g. OS X 10.7.5, Google Chrome 24.0.1312.52.
I have reproduced with a variety of OS and browser combinations. The problem is universal so far.

Please provide any additional information below.
This boils down to the dashboard CSS, I think. There is a fixed-width (18em) offset for the #dashboard-main div, which is not long enough for some team names.

Aside: Presenting a team's display name instead of the id allows team names with spaces to wrap, which helps in some cases.
david
#1 david
  • +Component-Dashboard
    +EasyFix
#2 hglo****@gmai***** (Google Code) (Is this you? Claim this profile.) 
I think the dashboard should anyhow show the group name instead of the group id.
When I first configured a group I was surprised by the display in dashboard, because
I assumed "id" is something internal and the "name" is the string that would be shown.
#3 maryelai********@gmai***** (Google Code) (Is this you? Claim this profile.) 
I'll try and tackle this.
#4 maryelai********@gmai***** (Google Code) (Is this you? Claim this profile.) 
I believe this bug has already been fixed. (Either that, or I'm having a lot of trouble reproducing it). For me, the group id gets split into multiple lines if it's really long. I tried it on both Firefox 24.0 and Chrome 29 on Ubuntu 12.04.
david
#5 david 
Looks like it is fixed. Thanks for the investigation!
  • +Fixed