I didn't notice this in the test instance, but the following is broken. I expect it to be an upstream issue, but just in case it's not, filing an internal bugreport.

If a search results in a change being brought up directly, for example, searching "Id619f8eabcaef5c11446c52e4a9f20839a0d172c", pressing the back button in a browser executes the search again instead of navigating to the previous page. This essentially results in being unable to navigate back beyond the last search, and invalidates any forward history, as the search execution acts as a new forward action.