{"id":"69e88c821ffe81f1664ec376","title":"2026 04 22 Issue 227","path":"how-to/committee/release-notes/2026-04-22-issue-227","contentMarkdown":"# 22-Apr-2026 — repeat pagination row below event list [closes #227](https://github.com/nbarrett/ngx-ramblers/issues/227)\n\n## [build 619](https://github.com/nbarrett/ngx-ramblers/actions/runs/24768904941) — [commit f2f2a5c](https://github.com/nbarrett/ngx-ramblers/commit/f2f2a5c779b2e334f7015b1d0bcfa619fbc35adb)\n\n_____\n\n- Adds a second pagination control underneath the walks listing, shown\nwhenever there is more than one page and the view is not the map. This\nmirrors the existing row at the top so that users who have scrolled to\nthe bottom of a long list - especially on mobile - can see at a glance\nthat more walks are available and page forward without scrolling back\nup.\n\n- Uses the same bindings as the top pagination (shared pageNumber,\npaginationTotalItems, pageChanged handler), so both controls stay in\nsync automatically.\n- see example screenshot below of repeated pagination where page contains enough scrollable content search that top pagination is out of view:\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/20d53bdd-ea5e-4eb0-b859-3028f470e94e.jpeg)","contentHtml":"<h1>22-Apr-2026 — repeat pagination row below event list <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/227\">closes #227</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/24768904941\">build 619</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/f2f2a5c779b2e334f7015b1d0bcfa619fbc35adb\">commit f2f2a5c</a></h2>\n<hr>\n<ul>\n<li><p>Adds a second pagination control underneath the walks listing, shown\nwhenever there is more than one page and the view is not the map. This\nmirrors the existing row at the top so that users who have scrolled to\nthe bottom of a long list - especially on mobile - can see at a glance\nthat more walks are available and page forward without scrolling back\nup.</p>\n</li>\n<li><p>Uses the same bindings as the top pagination (shared pageNumber,\npaginationTotalItems, pageChanged handler), so both controls stay in\nsync automatically.</p>\n</li>\n<li><p>see example screenshot below of repeated pagination where page contains enough scrollable content search that top pagination is out of view:</p>\n</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/20d53bdd-ea5e-4eb0-b859-3028f470e94e.jpeg\" alt=\"\"></p>\n"}