One response to a recent post about Advanced Search options was:

One thing I would like on the website in general is: I am someone who is slowly making my way through all of the dance music selections for the dance styles I’m interested in. I would like it very much if there was a way I could go directly to the page at which I stop instead of having to navigate slowly to the page I want. For example, if let’s say I stop on page 50, and when I return to the task again at another time and want to start on page 51, it takes many clicks to get there.

I responded with ways to hack the URL to reach a particular page in search results, and I still think saving the URL via a browser bookmark or your note-taking system of choice is probably the best answer to the specific question.  The URL encodes all of the details of the search, including the page that you’re currently on, so you get right back to where you left off.

However, the pagination system is a feature I implemented in 2012 and haven’t revisited¹ in detail since. At the time, the default pagination control that came with the UI library I was using worked perfectly well for the at most dozen (and generally more like two) pages of search results. That’s obviously not the case anymore.

I have been noodling with moving to an infinite scrolling system. This is the way many sites have moved to when presenting search results, and it would solve some other issues I’ve been having with limitations of the core indexing system I’m using. So, besides nudging me towards a more obvious way to go to a specific page in the search results, this comment may have stopped me from investing in an alternative scheme that would have made this even harder. Thank you!

I am going to continue to think about this some more. Including options like making the “my searches” list encode the page that you were last on. I don’t want to keep the page as a core part of the saved searches, since I want to show you the searches you do most frequently, but this shouldn’t prevent me from keeping a separate field for the most recently visited page for each search.

But the absolutely straightforward answer is to replace the textual indication of what page you’re on with an editable number. I did that, so now hopefully new users can easily get to a specific page in their results without digging too deeply.

Just type the page you want to in the edit control, press Enter/Return, and the new page will load.

As always, please let me know if you have any thoughts about the subject of this post or the site by commenting below or using other feedback mechanisms listed here. And if you enjoy the site or the blog (or both), please consider contributing in whatever way makes sense for you.

1. Ironically, I’ve re-implemented the exact same system a couple of times, once when moving to Vue.js, and again when moving to Vue3 and BootstrapVueNext. Even more ironically, getting the pagination control to work correctly in BootstrapVueNext was my first major contribution to that project… ↩︎