Back/Forward: How often does it work?

[GoogleCodeExporter]

What steps will reproduce the problem?
In ESV/Rev 1, I tried it out in different situations:

1. Next: 
- 9 times (to Rev 10)
- Back: 9,8,7,1

2. Bible Navigator (= BibNav):
- 9 times from Jud to Phm
- Back: Heb, 1Pe (leaves out Jam)

3. BibNav with chapter numbers:
- 9 times, from Rev 1 to Rev 10
- Back: 9,8,7,5,4,3,1

4. Ref bar, with chapter box
- 9 time, from Rev 1 to Rev 10
- Back: 9,8,6,1 

What is the expected output? What do you see instead?
How often does Back work?
Is there any rule for this (I am in the process of writing a manual of xs and 
try to describe how Back/Forward works together with other tools 

What version of the product are you using? On what operating system?
xs 3.4 linux/firefox

Please provide any additional information below.

Original issue reported on code.google.com by wolfgang...@wycliff.de on 18 Jun 2012 at 6:06

[GoogleCodeExporter]

Using a mix of tools, it works OK:
Jhn 1 (next) -> Jhn 2, (up-arrow) -> Jhn 3, RefBar/chapter: typing 4 -> Jhn 4, 
Bible Navigator: Jhn 4 -> Jhn 5.
Now using Back several times: Jhn 4,3,2,1.

On the other hand, using a mix of only two tools (next and up-arrow) in 1Co 10 
times, using Back has chapter omissions again.

Original comment by wolfgang...@wycliff.de on 18 Jun 2012 at 6:20

[GoogleCodeExporter]

Left and right arrow (for Back/Forward) show the same behaviour.

Original comment by wolfgang...@wycliff.de on 18 Jun 2012 at 6:22

[GoogleCodeExporter]

Looking at the history, I see the holes (chapters not recorded there).
Checking the assumption, that the problems depends on the speed, how fast the 
next reference is chosen, I tried the following:
- changing the reference by any of the tools and counting to three (making a 
pause), it all works OK (even using the same tool like next or up-arrow).

-> Would it be possible to store  (keep in memory) the 
reference-changing-commands if they cannot be applied immediately?

Original comment by wolfgang...@wycliff.de on 18 Jun 2012 at 6:29

[GoogleCodeExporter]

Yes, there is a 3 second delay before a page is recorded in history.

Especially since the verse number is recorded along with book and chapter, a 
delay is necessary. Otherwise, while, traversing verses (or chapters) every 
single mid-point would be recorded. This would fill up the history bar with 
unneeded information.

Original comment by gpl.prog...@gmail.com on 27 May 2013 at 9:16

• Changed state: WontFix