Investigate maintaining a state so the back-button works.

Created on 12 February 2016, over 8 years ago
Updated 10 July 2023, 12 months ago

Problem/Motivation

Not sure if this is feasible or even a useful user experience, but if you scroll to page 10, click an item and then click back, you will loose your state. This is probably the expected behavior, but it might be possible to automatically open N pages worth of content based on how far the user got.

Proposed resolution

See if this is worth solving.

Remaining tasks

  • Come up with some possible solutions.
  • Write a patch.
  • Make sure it's tested.

User interface changes

None.

API changes

None.

Data model changes

None yet...

✨ Feature request
Status

Needs work

Version

2.0

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia Sam152

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¦πŸ‡ΉAustria attisan Vienna

    #78 + views_ajax_history β†’ = this is the way πŸ’ͺ

  • Status changed to Needs work 12 months ago
  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thanks all! Could this please be reworked as MR?

    Furthermore I'm unsure if we should really merge it without being a separate option, that can be disabled. I think we should first have tests for this module to ensure it doesn't break important functionality.

Production build 0.69.0 2024