Rollback doesn't refresh the editor

[skttl]

When rolling back from the history pane in the info tab, the content in the editor stays at the version you rolled back from. You have to reload the page, in order to se the rolled back content. This can be confusing, as I would expect to be able to just rollback, save and publish and have my changes reverted.

But instead, I need to roll back, reload the page, then save and publish.

Reproduction

Open a page and make some changes.
Save those changes.
Roll back to the previous version using the rollback button in the history group in the info pane.
Note that the content is still the newest content. Here I would expect the content to be the content I rolled back to.

Refresh the browser, to see the active content is not the newest anymore (as you would expect it to be).

Both v7 and v8 does this.

[nul800sebastiaan]

We would welcome you to have a look at this in v8 (we're not creating bigger new features like this for v7 any more).

The tricky part here is surely that we would need to only refresh the editing area and I don't know how to hook into that. However, when we go into infinite editing and update the document type of the current page, we also do a refresh of the editing area so perhaps this could be a similar thing.

[umbrabot]

Hi @skttl,

We're writing to let you know that we've added the Up For Grabs label to your issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post

Thanks muchly, from your friendly PR team bot :-)

[bjarnef]

It seems to be related to this PR I submitted where the image cropper image and grid content disapear on rollback. #5792

[skttl]

Just tried this one again on bleeding edge v8/dev and can't reproduce. So something must have fixed it :)

[nul800sebastiaan]

Ah, I didn't notice it was a duplicate! Yep, fixed yesterday! #6349 👍