Outside of CMSMain (e.g. for a non-inline-editable elemental block), the history tab (powered by HistoryViewerField) displays its own preview of the record.
It doesn't take into account that there's already a preview panel open previewing the main record, so you end up with two preview panels - the normal one, and the history viewer one.
The history preview panel is only as high as the version table, so if there's not many versions you have to scroll to see much of anything.
Possible solutions
- When a
HistoryViewerField is displayed, hide the main preview panel completely, so we only have the history viewer preview panel. This is consistent with the behaviour in CMSMain.
- Find a way for
HistoryViewerField to hijack the existing preview panel (it does have a JS API so that should be doable)
Related issues
Outside of
CMSMain(e.g. for a non-inline-editable elemental block), the history tab (powered byHistoryViewerField) displays its own preview of the record.It doesn't take into account that there's already a preview panel open previewing the main record, so you end up with two preview panels - the normal one, and the history viewer one.
The history preview panel is only as high as the version table, so if there's not many versions you have to scroll to see much of anything.
Possible solutions
HistoryViewerFieldis displayed, hide the main preview panel completely, so we only have the history viewer preview panel. This is consistent with the behaviour inCMSMain.HistoryViewerFieldto hijack the existing preview panel (it does have a JS API so that should be doable)Related issues