Idea Summary

On typical server-side rendered pages (like Google), pagination triggers a full page load. If you then use your browser's back button, you'll return to the previous page in the pagination sequence.

While using this ideas app on mobile, I instinctively tried to swipe right to go back to the previous pagination page. Instead, I was taken all the way back to Google, where I initially entered the app.

Therefore, I propose a new attribute. When enabled, pagination within a Template Component would utilize the History pushState API. This would allow browser back navigation to correctly go to the immediate previous pagination page.

I am aware that this is a rare scenario, but for mobile UX, Template Components often serve as the main entry point to deeper pages. 

Use Case
Mobile UX optimized apps