- On a Flow board click on 'View history' - try to find a board with not too extensive history - the number of history entries is <500.
- In 'View history' - click on the option '500' in the pagination control - the pagination control will disappear.
Description
Related Objects
Event Timeline
This is intentional behavior, and the same for core. See e.g. https://en.wikipedia.org/w/index.php?title=Tony_Smith_%28Victorian_politician%29&offset=&limit=500&action=history and https://en.wikipedia.org/w/index.php?title=Tony_Smith_%28Victorian_politician%29&offset=&limit=50&action=history .
(Demo will break if there get to be more than 500 entries on that page, but you get the idea).
Suggest closing.
To return to history pagination controls, a user should click on the browser's back button - which is not so convenient.
They can also just click the history tab to get the default settings (which may or may not require pagination). But they don't really need to paginate if all entries are already on the screen.
I can see the argument that it could be clearer to explicitly show that pagination is not necessary (e.g. show the full pagination bar but have 'newest' and 'oldest' unclickable, similar to how it is if pagination is required, but you're at the beginning or end).
But if we want to change this, I suggest doing so in both core and Flow. Otherwise, people will definitely object to the inconsistency.
Declining this because this is also how pagination works in core. We could file a bug against core to change this, because it doesn't seem like ideal UX to me.