In #2683021: Integrate with jQuery bbq we are talking statefulness, here's a second one. In certain situations (i. e. transporting query strings in views; I actually have such an issue, but just think of "destination"), the query parameter is part of a lazyloaded content, and then used for a back-reference to the actual view, you will land on a different page than the one you came from (and worse, as an occasional user, you'd probably find it difficult to get to the previous results, too).

TL;DR: I think an option that detects the "page" parameter and then somehow (we'll figure) restore the appropriate state? It could also be catched at early bootstrap and redirected to the solution we would have for the related issue (so we could re-use some whatever cache solution, if we find a sensible one).

What do you think?

Comments

doitDave created an issue. See original summary.

doitDave’s picture

For the records and for discussion, too: I just figured that a very simple improvement would be to extend lazyloading in both directions. I. e., not only the "next" page when reaching a bottom threshold, but also the "previous" one when on a ?page=n and at the top.
Such an approach should give a real improved intuitive experience and should be quite simple to implement. I would sketch a draft. Opinions?

doitDave’s picture