Persist UI state on URI #378

New issue

Closed

opened 2024-03-26 23:15:13 +01:00 by blacklight · 1 comment

blacklight commented

2024-03-26 23:15:13 +01:00

Owner

This should probably be implemented on a per-integration basis.

When moving through different views, or changing the state of the UI, we should also persist the new state on the URI fragment (e.g. #/view=foo&state=bar), so the same view/state can be restored when the user navigates back to the page.

This should probably be implemented on a per-integration basis. When moving through different views, or changing the state of the UI, we should also persist the new state on the URI fragment (e.g. `#/view=foo&state=bar`), so the same view/state can be restored when the user navigates back to the page.

blacklight added the

enhancement

labels 2024-03-26 23:15:13 +01:00

blacklight added this to the ui project 2024-03-26 23:15:14 +01:00

blacklight self-assigned this 2024-04-12 22:13:05 +02:00

blacklight referenced this issue

2024-07-27 11:22:44 +02:00

[UI] Implement history management / dynamic back button behaviour #416

blacklight commented

2025-02-09 18:03:33 +01:00

Author

Owner

Many integrations now have their state persisted on the URI.

I'll close this issue and gradually implement URI state persistence on the remaining integrations.

Many integrations now have their state persisted on the URI. I'll close this issue and gradually implement URI state persistence on the remaining integrations.

blacklight closed this issue

2025-02-09 18:03:33 +01:00