tree a992c28489878f5b781ac944ab9f2f6ffe8fe4e1
parent 4dfd80fe2d0a16f3fd9c898fee129b34f1a07c47
author Ben Rohlfs <brohlfs@google.com> 1620813890 +0200
committer Ben Rohlfs <brohlfs@google.com> 1620815526 +0200

Fix fully reloading the change view when the new patchset is unknown

We are trying to avoid fully reloading all change view resources when
the user just switches to a different patchset. But did not have a check
for whether the new patchset that the user wants to switch to is
actually known already.

This problem surfaced in the referenced issue when you were saving an
edit and the change would not know about this new 'edit' patchset, but
still trying to avoid the full reload.

This bug has not surfaced before, because we are now more aggressive
(since change 305575) about reusing the change view.

Bug: Issue 14521
Change-Id: I085bb9ced6ac4e7f48a1271dba0c855a4a85e279