Bug 1273299

Summary: evince history previous and next history button do not work
Product: Red Hat Enterprise Linux 7 Reporter: Oliver Ilian <oliver>
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-20 12:56:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Oliver Ilian 2015-10-20 07:36:27 UTC 
Description of problem:
When you open a PDF in Evince, that "Go to previous/next history item" buttons have no function (grayed out)
I am not sure what is meant by "History item" but users are expecting to move between pages with this buttons

Version-Release number of selected component (if applicable):
evince-3.14.2-5.el7.x86_64

How reproducible:
Every time you open a PDF

Steps to Reproduce:
1. open a PDF
2. see that the buttons in the top left are grayed out

Actual results:
Buttons are not working

Expected results:
Jump forward and backwards between pages
Comment 2 Marek Kašík 2015-10-20 12:56:54 UTC 
(In reply to Oliver Haessler from comment #0)
> Description of problem:
> When you open a PDF in Evince, that "Go to previous/next history item"
> buttons have no function (grayed out)
> I am not sure what is meant by "History item" but users are expecting to
> move between pages with this buttons

The buttons have the same meaning as the back and forward buttons in your browser. The back button become active when you click on a link on a page or on an item in the index. If you use the back button you will get also the forward button active so you can go forward in your history.
It works for me as expected so this is not a bug.

Regards