On 11/8/20, James Tomasino <tomasino at lavabit.com> wrote: > I'm not 100% sure if it requires caching or not, but what I would want from > a client with a back button is to take me back to where I was in the > document's scroll position before I clicked. Some clients are already > handling this use case (hooray!). This may be a greater concern for > graphical clients than text ones, unless the client is handling paging > itself. Losing your place can be frustrating when moving through a series of > inter-linked documents. Imagine going through older CAPCOM articles, for > instance. Every time you click back needing to scroll back down to wherever > you were becomes obnoxious and a reason to just stop. Now in that case, if the client does not cache, the page is reloaded. Even if the client remembers the position where you were before in that page, imagine the scenario where the page gets changed before reloading (say, new links added to (or removed in) that page), then you have to scroll anyway. (In the worst case, imagine the link you clicked does not exist in the new page.) > Again, I'm not sure if caching is involved in it or not, but that's the best > thing I could come up with as an answer to your question. So caching is required. Your client must keep that page in cache along with your last position in that page for the feature you want. ~smlckz
---
Previous in thread (40 of 55): 🗣️ Ali Fardan (raiz (a) stellarbound.space)
Next in thread (42 of 55): 🗣️ Waweic (waweic (a) protonmail.com)