Closed Bug 1185977 Opened 5 years ago Closed 4 years ago

A Scroll Bar is displayed in Loop Panel for a long Conversation Name

Categories

(Hello (Loop) :: Client, defect, P3)

defect

Tracking

(firefox40 affected, firefox41 affected, firefox42 affected)

RESOLVED WORKSFORME
Tracking Status
firefox40 --- affected
firefox41 --- affected
firefox42 --- affected

People

(Reporter: vasilica.mihasca, Unassigned)

Details

(Whiteboard: [UI bug])

Reproducible on: Firefox 42.0a1, Firefox 41.0a2 and Firefox 40.0b6 across all platforms

STR
1. Start Firefox.
2. Click Hello icon.
3. Start a conversation.
4. From conversation window click 'Add some context'.
5. Edit the Conversation name entering a string longer than 45 characters (e.g. Pneumonoultramicroscopicsilicovolcanoconiosis )
6. Check the Conversation name in the Loop Panel

ER
In Loop Panel should be displayed a limited number of characters, interrupted by ellipsis (e.g. Pneumonoultramicroscopicsi...). Hovering on the conversation name, an explanatory tooltip panel should appear, displaying the entire conversation name. 

AR
A Scroll Bar is displayed in Loop Panel when the conversation name is a string composed from minimum 45 characters.

Additional notes:
- This issue is reproducible on Firefox 42.0a1 (2015-07-20), Firefox 41.0a2 (2015-07-20) and Firefox 40 Beta 6 (20150720220238) under Windows 8.1 32-bit, Ubuntu 14.04 32-bit and Mac OS X 10.10.
- I am attaching a screenshot: http://i.imgur.com/rkgobe8.png
I forgot to mention that this issue is not a regression.
what would we prefer long conversation names do?
Rank: 35
Flags: needinfo?(sfranks)
Priority: -- → P3
Whiteboard: [conversation] → [UI bug]
Trail off to elipses at the end as suggested above. I believe this was specified elsewhere in a bug (but I can't for the life of me remember which bug).
Flags: needinfo?(sfranks)
I'm pretty sure this has been fixed (now that room names follow document titles, they are frequently very long, and seem to be truncated properly)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.