Bug 859793 - [WebTrans] text in source messages can no longer be copied
Summary: [WebTrans] text in source messages can no longer be copied
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 2.0
Assignee: Patrick Huang
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-24 04:21 UTC by Ding-Yi Chen
Modified: 2012-11-07 06:19 UTC (History)
2 users (show)

Fixed In Version: 1.8.0-SNAPSHOT (20120925-0027)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-07 06:19:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Ding-Yi Chen 2012-09-24 04:21:59 UTC
Description of problem:
In WebTrans, text in source messages can no longer be copied by the regular copy text method (i.e. highlight the text then press ctrl-c or right click and select Copy).

This affect the usage, as translator might copy the part of the source message and paste the text as search terms to get more information.

This can be produce in both Firefox and Chrome.

Version-Release number of selected component (if applicable):
Zanata version 1.8.0-SNAPSHOT (20120921-1422)

How reproducible:
Always

Steps to Reproduce:
1. Visit any document.
2. Highlight any text in source messages.
3. Right click on the highlighted text
  
Actual results:
No "Copy" appeared in the right-click menu.
Nor the keyboard shortcut (Ctrl-C 

Expected results:
"Copy" function appears in right-click menu
and works successfully.

Additional info:
This symptom does not occur in 1.7 Servers.

Comment 1 Patrick Huang 2012-09-24 07:21:37 UTC
Committed into master:
https://github.com/zanata/zanata/commit/ab1291fb2eaa40f3517cef1bb108a8cc79012743

Comment 2 Ding-Yi Chen 2012-09-25 01:20:37 UTC
VERIFIED with Zanata version 1.8.0-SNAPSHOT (20120925-0027)

Comment 3 Sean Flanigan 2012-11-07 06:19:32 UTC
Fix released in Zanata 2.0.


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