Bug 1096995 - TM pane is extended when a translation memory contains a long string which cannot be wrapped
Summary: TM pane is extended when a translation memory contains a long string which ca...
Keywords:
Status: CLOSED DUPLICATE of bug 1000199
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-12 23:11 UTC by Yuko Katabami
Modified: 2014-05-13 00:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-13 00:38:21 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1078865 0 unspecified CLOSED Content in the TM is not completely viewable 2021-02-22 00:41:40 UTC

Internal Links: 1078865

Description Yuko Katabami 2014-05-12 23:11:34 UTC
Description of problem:
TM pane is extended when a translation memory contains a long string which cannot be wrapped.
It makes extremely difficult to read the information.
You need to scroll to the right to be able to read one line, and when you need to see the next line, the beginning of the next line is invisible and have to scroll back.

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


How reproducible: always


Steps to Reproduce:
1. Find a long string that is not broken with spaces
2. Check TM pane


Actual results:
It stretches beyond the width of the window


Expected results:
It should be wrapped so that you don't need to scroll side to side.

Additional info:

Comment 2 Ding-Yi Chen 2014-05-13 00:38:21 UTC
This is quite similar to Bug 1078865. Yet I think it would be best to merge into Bug 1000199 for designers and developers to have better and consistent design.

*** This bug has been marked as a duplicate of bug 1000199 ***


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