History should restore scroll position when going back

[yuzijie]

I think it is better if you can go back to the position where you previously clicked, instead of the beginning of previously tiddler.

One of the advantages of tiddlywiki is its ability to jump between tiddlers. However, when you jumped back to a long tiddler, you have to look for where you left off before continuing, that is quite annoying.

Is it possible to add a record in history list when you clicked a link, and go back to that link when you hit the back button?

[Jermolene]

Hi @yuzijie handling link navigation long tiddlers can definitely be awkward for users at the moment.

I'd like to add a story view that has the tiddlers arranged in horizontal columns, making it easier to track backwards and forwards without scrolling.

There is also the idea you suggest of extending the history mechanism so that it records the scroll position within the tiddler, and can return to the same scroll position. I've amended the title of this ticket to reflect that idea.

[tobibeer]

I think (other than enabling the browser's back button) this is a very useful functionality and I suggest to implement it like in that picture of #133

(as for an "unobtrusive permalink", I'd like to see a title-click behavior doing that ... a user needs to know it => no "title" attributes)

Only now, when you hover the title / tiddler / "gutter", you get a kind of "back"-arrow that allows you to jump back to the link you clicked to open the tiddler... insofar as it is still open..

«

<

Here's how that could work...

1. when an internal link is clicked, the link is given a "link-origin" attribute storing a unique id
   • preferably a UUID generated via $tw.utils.newUUID(), so that plugins can also make use of it!
2. in a global object which is not persisted beyond the session, e.g. $tw.origins, a hashmap is stored whereas for each tiddler title the link-origin of a link having opened it is stored
3. the "jump back" button is rendered by a macro which — when a corresponding link-origin is found — renders a button providing the required on-click behavior

The one problem though that begs for a general solution: How does an attribute survive a refresh? It would be nice if widgets had a way to do a pre-refresh routine to store away attributes that need to survive it.

[Jermolene]

Hi @tobibeer I'm not sure that it's a good idea to introduce a new UI for navigating the history; what's wrong with using the browser back/forwards buttons as usual?

[tobibeer]

The default history only scrolls to the tiddler, I presume, not the link that was clicked. One could highlight or flash that link so as to show "this is where you came from"... at its scroll-position.

[Jermolene]

The default history only scrolls to the tiddler, I presume, not the link that was clicked. One could highlight or flash that link so as to show "this is where you came from"... at its scroll-position.

See what I said above:

There is also the idea you suggest of extending the history mechanism so that it records the scroll position within the tiddler, and can return to the same scroll position. I've amended the title of this ticket to reflect that idea.

I think that that does what you're asking for.

[tobibeer]

Oh, sorry for that... didn't read carefully all the way to the end.