Page History

Summary

Actionbar -> sections -> groups -> items

sections can be shown/hidden

groups and items can be actionbar - enabled/disabled visible/hidden

based on selected node/item (not all actions operate on a node/item)

based on roles

In page editor we enable/disable actions in the actionbar based on which permissions the current user has for the selected component/area.

In dam we enable/disable based on wether the asset is a master (this is probably outdated logic).

We typically hide/show sections based on node type - and enable/disable groups to control if edit actions or add actions should be shown. This is not always the case.

In Pages browser we show activateRecursively only if there are sub pages.

In Security app we enable/disable adding or editing actions based on if the selected node is /admin or /system. Can only edit below these nodes and only add on these nodes.

For redo/undo we will enable/disable based on the undo history size.

Availability

Problem

The action bar can take several states within one sub-app.

...