Scope: Shared state model for Experience blocks
Block states entries are optional and support three id classes:
hover, active, focus, enabled, readonly, visited, selected, disabledmedia-print, media-below-768, media-above-1200sxxxxxx matching ^s[a-f0-9]{6}$State entry shape:
idname?activation?.when? for datum-driven states. A datum reference's path (on datumReference, or on datumCondition.datum) selects the value the state is evaluated against. Paths in the meta.* namespace (for example meta.isDirty) resolve from the datum's runtime metadata rather than the entity value.overrides as partial block propsMedia states do not require activation expressions.
A data state applies its overrides while a datum value is set, or while it matches a condition. Use one to restyle, show or hide a block from data, for example colouring a task chip by its status.
sxxxxxx), and you can rename it from its state menu.State ID | Label | Emitted CSS |
|---|---|---|
|
| |
| Small screens (below 768px) |
|
| Large screens (1200px and up) |
|
Availability:
Shared block props include print/page break controls.
Property | Type | CSS property |
|---|---|---|
|
|
|
|
|
|
|
|
|
These properties can be set directly on a block or through state overrides (including print-only media states).
display accepts:
noneinline-flexflexinline-gridgridWhen display: none is set through a media state (for example media-print), the block is excluded for that media context and layout reflows naturally.