Page state too long for URL

Issue description

In rare cases the state encoding in the history leads to URLs that are too long. When the users goes back he will not find the page (in the state he left it), but rather have a blank browser page with the the respective error message.

Developer comments

In the case at hand it was module contents was viewed. After leaving the back and returning with history back, then described behavior was observed.

There is two parts to this issue. * If the page state is very long, [14483, it should simply be ignored], since it is worse to click return and see the URI too long error message from the web browser than just seeing a page that does not reflect the exact state it was left at, but rather its initial state. * The problem arises when there is many (> 100) components on a page which preserve state. But actually not all of these components do need to preserve their state since only the ones the user interacted with actually have a changed state. [14482, Consider this when computing the state of a page.]

Reporting date

2025-02-25

Reported by

Robert Cerny

Resolving date

2026-01-20

Resolved by

Robert Cerny

Resolved in version

Topincs 10.1.0 – next release

Related to2

Only changes should be considered in state preservation(Change)

Do not preserve state when URI would get too long(Bug)