Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 747228

Summary:	Translation editor: Cannot change page by entering number on page indicator.
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-UI	Assignee:	Alex Eng <aeng>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ding-Yi Chen <dchen>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.4.1	CC:	aeng, hpeters, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	1.4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-28 07:02:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	743789

Description Ding-Yi Chen 2011-10-19 07:24:19 UTC

Description of problem:
In message list view of a document that has multiple page, it is expected that certain page can be viewed by entering page number in the page indicator and press "enter". However, this function is no longer working in 1.4.2-SNAPSHOT

Version-Release number of selected component (if applicable):
Zanata version 1.4.2-SNAPSHOT (20111019-1122)
1.4.1 does not have this problem, however.

How reproducible:
Always

Steps to Reproduce:
1. Visit a document that have multiple pages, such as UserGuide->Playing_multimedia
2. Click on page indicator, type 3, then press enter.
  
Actual results:
Translation Editor still showed page 1.

Expected results:
Translation Editor change to page 3.

Comment 1 Alex Eng 2011-10-20 05:01:37 UTC

Fixed. See https://github.com/zanata/zanata/commit/4c7f0e77cf518f4c61ef58b7d3c0ec333826ec95

Comment 2 Ding-Yi Chen 2011-10-21 01:59:08 UTC

VERIFIED with Zanata version 1.4.2-SNAPSHOT (20111021-1030)

Comment 3 Hedda Peters 2014-03-26 04:35:01 UTC

I just encountered this problem again in 3.3. 
Exact same problem & steps to reproduce as described in original bug report.

Using FF 17 if relevant.

Comment 4 Hedda Peters 2014-03-26 04:37:10 UTC

Aaaah - sorry. Spoke too soon.

It all works, I got myself confused.