tree dbdf5b33d7baff6152b67647b6e493a13fa53072
parent 5eb1baaeab6cf6df85514592dc06a2f0d9a725a1
author Ben Rohlfs <brohlfs@google.com> 1666080346 +0200
committer Ben Rohlfs <brohlfs@google.com> 1666081994 +0000

Fix browser 'back' for search result pages

The router should not set the `changes` when handling the route. The
search view model is taking care of that. The router should only update
the state, not set it. So only `query` and `offset` are set by the
route handler.

The view model change loading is only triggered by changes to `query`
and `offset`, so it would work the first time, but after browser back
the model would not react, because there was no change to those two
properties. That is fine, but then `changes` should not be reset to []
at the same time.

When using `updateState` instead of `setState` we have to explicitly
use `offset: undefined` in the router to clear it.

Release-Notes: skip
Google-Bug-Id: b/254179414
Change-Id: I8bc53bb0c6be648b89179b39dfe5da48172bb2b8