You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a reader, when I follow a link (inline, in the TOC, move nav. slider) to a new position in the text, I want to be able to get back to my previous position.
If a reader follows a link and moves forward in the text, present a link to move back in the text to the previous location.
If a reader follows a link and moves backward in the text, present a link to move forward in the text to the previous location.
If a reader follows a link forward or back to their previous location, present a link to return to previous position.
The text was updated successfully, but these errors were encountered:
If the reader is made aware of when the URL changes, could the browser back/forward buttons be sufficient? (The reader is updating history now but doesn't react when you use the back/forward buttons.)
I think that is a sensible and agile first step, but...
If using the back/forward buttons on the browser, it's important that the webpage/app doesn't completely re-load to support the use of case of Gabii (don't want to reinitialize the load of the WebGL object).
Supporting history is addressed in #135 --- some questions that arise:
the browser history is ... monotonous, and none of the history API currently affects the title of items. I don't think we want to make the title even longer. Maybe the title + percentage?
do you have an idea of visible controls? I will confess that when I try to imagine back/forward I hear someone on DAT saying stop that, the browser already has those buttons :-)
As a reader, when I follow a link (inline, in the TOC, move nav. slider) to a new position in the text, I want to be able to get back to my previous position.
The text was updated successfully, but these errors were encountered: