openstreetmap
Add next page button at bottom of changesets
We read down to the bottom of a changeset, e.g., https://www.openstreetmap.org/changeset/175272266 and want to see the next page, and think
I could have sworn this changeset had more than one page. Let me double check.
And scrolling back up reveals
Yup, sure enough, there are three pages.
Therefore I suggest an additional "next page button", in fact the same buttons as in the picture, should be added down at the bottom too, but before the final
Changeset XML · osmChange XML
section.
If I understand correctly, you are pointing out that the pagination controls appear at the top of these lists, instead of at the bottom where they would normally be expected in other apps, right?
By the way, one detail that may not be obvious is that each section "Ways", "Relations", "Nodes"" has its own pagination, so it's possible to paginate independently in each. Here's an example of all three on display: https://www.openstreetmap.org/changeset/175393853
It's also worth comparing with the pagination for the version history of a feature. For example, https://www.openstreetmap.org/way/61652364 has 7 versions at the moment. These can be accessed with a pagination control that sits at the bottom of the panel, under the footer (as delimited by the horizontal separator line).
So I agree that it's all a bit inconsistent! 🙂
Seems like each item needs a page control at both top and bottom of it,
Page control
Page control
Guts
Page control
Page control
Guts
Page control
Page control
+1 on this. Replicating the "Next" button and page numbers at the bottom seems like the best approach here. It effectively solves the "scroll-back" friction users face when reaching the end of the list.
Also, sticking to the same button design as the top controls maintains UI consistency, which is definitely preferable to introducing a different pattern (like a dropdown) just for the footer.
I'm not sure about having the pagination controls both above and below their respective sections. I think it would become too busy. To me the bottom-only is more in line with common expectations in applications.
Having said that: happy to see proposals 🙂