Bug 802189 - Horizontal scroll bars on msgid where line break should be used
Summary: Horizontal scroll bars on msgid where line break should be used
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 1.5
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
: 2.0
Assignee: Alex Eng
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 00:34 UTC by Hedda Peters
Modified: 2012-11-07 06:18 UTC (History)
3 users (show)

Fixed In Version: 1.8.0-SNAPSHOT (20120928-0032)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-07 06:18:47 UTC

Attachments (Terms of Use)
Scroll Bars where line breaks should be used (234.86 KB, image/png)
2012-03-12 00:36 UTC, Hedda Peters 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 807506 0 unspecified CLOSED word breaks are incorrect in translation editor using Chrome 2021-02-22 00:41:40 UTC

Internal Links: 807506

Description Hedda Peters 2012-03-12 00:34:35 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

Before editing, long mgsid messages are correctly broken into several lines. As soon as you click into a message to open the editor, the msgid uses a horizontal scroll bar instead of retaining the line breaks. After leaving the editor again, the scroll bar remains.
Any view using a scroll bar is detrimental for translating, should be used only when line breaks are impossible. 


Reproducible: Always




Seen on FF 3.1 and F 9.0.1
Comment 1 Hedda Peters 2012-03-12 00:36:43 UTC 
Created attachment 569242 [details]
Scroll Bars where line breaks should be used

Screenshot attached
Comment 2 Runa Bhattacharjee 2012-07-30 13:35:14 UTC 
Is this still happening for 1.6 and above? Thanks.
Comment 3 Alex Eng 2012-09-27 00:29:13 UTC 
Problem fixed in Version 2.0  

See https://bugzilla.redhat.com/show_bug.cgi?id=807506#c3
Comment 4 Ding-Yi Chen 2012-09-28 03:07:05 UTC 
This problem still exists in Zanata version 1.7.4-SNAPSHOT (20120928-0009)
but fixed in Zanata version 1.7.4-SNAPSHOT (20120928-0009)

VERIFIED with Zanata version 1.8.0-SNAPSHOT (20120928-0032)
Comment 5 Sean Flanigan 2012-11-07 06:18:47 UTC 
Fix released in Zanata 2.0.
Note You need to log in before you can comment on or make changes to this bug.