History of Elemental Blocks is not reflected correctly on the history of a Page

[pjayme]

When changes are saved or published within elemental blocks then these changes are not reflected on the history of a Page. Instead, it takes the most recent record and updates its “Block History” where the correct changes are shown:

• The issue here is that changes made within a content block are not immediately visible to the user when the history of a page is viewed which could lead to the impression that no changes have taken place.
• Users have to take an additional step by clicking on the “Block History” of a block to view the accurate set of changes.
• Prior to clicking on the “Block History” the state that is shown on the history of a page shows an outdated version of the block which could lead to further miscues. Ideally, the state that is shown on the page level should at least reflect the most recent state of the block.
• It would be handy if the "Block History" was integrated into the "Page History" using a single view instead of having these two entities as separate views that can lead to misleading history reviews for content editors.

CMS: 4.12.1
Framework: 4.12.4
Elemental: 4.10.2

Steps to reproduce:

1. In the CMS, create a page
2. Make changes to the Content of the page and hit Save
3. Go to the "History" tab and check that a new record is created for the latest changes
4. Go back to the main tab of the page, create a new content block and save the content block
5. Go to the "History" tab and see that no new record is created to reflect the creation of the content block
6. Make changes to the content block and hit save
7. Go back to the "History" tab and see that no new record is created from the changes made to the content block

[maxime-rainville]

Maybe the silverstripe/versioned-snapshot-admin module might be able to help here?

[MarkCondello]

Is there an ETA on this bug / issue being worked on?
Our client has reported inconsistent behavior for Block history and would like to resolve it asap.