TYPO3 Core

this is caused probably by the
.defer(500) in the ContextMenuActions.js

currently is (in v8):

top.TYPO3.Backend.ContentContainer.setUrl(
     top.TYPO3.settings.RecordCommit.moduleUrl + ....
    );
      if (table === 'pages' && top.TYPO3.Backend.NavigationContainer.PageTree) {
        top.TYPO3.Backend.NavigationContainer.PageTree.refreshTree.defer(500);
     }

top.TYPO3.Backend.ContentContainer.setUrl(
      top.TYPO3.settings.RecordCommit.moduleUrl + '&redirect=' + ContextMenuActions.getReturnUrl() ...
         ).done(function () {
      if (table === 'pages' && top.TYPO3.Backend.NavigationContainer.PageTree) {
           top.TYPO3.Backend.NavigationContainer.PageTree.refreshTree();
         }
      });

It was changed in 9 in here:
https://review.typo3.org/#/c/51594/113/typo3/sysext/backend/Resources/Public/JavaScript/ContextMenuActions.js

Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55233

Tymoteusz Motylewski wrote:

Applied in changeset 17136ee9f2bfc29268b1676a56f96eb6d97b59aa.

This patch reloads the page tree on every load event. To reproduce disable a page and then edit a content element. The Page tree reloads on every button click on the main frame. The load event should be removed after execution.

i opened a new bug #84294 and committing now a patch