Bug 772820 - Notification message wraps despite having sufficient width
Summary: Notification message wraps despite having sufficient width
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 1.5-SNAPSHOT
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Runa Bhattacharjee
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-10 02:56 UTC by David Mason
Modified: 2013-03-04 02:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-07-20 00:52:21 UTC
Embargoed:


Attachments (Terms of Use)

Description David Mason 2012-01-10 02:56:54 UTC
Description of problem:
In translation editor, when the browser window is narrow or the project/document name is long, notification messages (e.g. save notifications) wrap to 2 or more lines and are not fully visible as they extend below the blue bar. There appears to be sufficient space to the right of the save notification so it should not need to wrap.
When viewing a multi-module project with long path names, 1600px was sufficiently narrow to cause wrapping, and the notification was completely invisible with widths less than 1500px.


Version-Release number of selected component (if applicable):


How reproducible:
Varies with document path length


Steps to Reproduce:
1. Open a document with long path names
2. Reduce the browser width
3. Save changes to a translation unit
  
Actual results:
Notification displays wrapped and partially visible, or not at all.

Expected results:
Notification is completely visible when browser width is 1024px or greater.

Additional info:
Document path/name also appear to be cut short sometimes.

Comment 1 Alex Eng 2012-07-20 00:52:21 UTC
Bug is not reproducible with notification interface changed in 1.7.

New notification display is a windows on top right side with scroll if too long.


Note You need to log in before you can comment on or make changes to this bug.