Any change to a patch revision, sends user back to the initial revision on reload
We should probably store the revision the user is visiting so that we put the user back on that same revision after a comment creation instead of sending them to the initial one.
Either that or we don’t reload the whole view, but just put the comment in the DOM after the request finishes.
Ok so based on my work on draft patch reviews, I can now say that any change like creating new reviews, publishing them, etc. requires the reload which pushes user to the initial revision.
Not reloading the whole view would be nice but could get messy. What about if we could reload the whole view but persist the revision id the user was on so we don’t switch tabs for them.
wfm