mosaic-core/dev.catbit.mosaic.core.data.schemas.tile.tiles.grouping/AdaptiveVisibilityTileSchema

AdaptiveVisibilityTileSchema

@Serializable

@SerialName(value = "AdaptiveVisibility")

data class AdaptiveVisibilityTileSchema(val id: String, val tiles: SerializableImmutableList<TileSchema>, val events: SerializableImmutableList<EventSchema>?, val style: StyleSchema, val searchableTerms: SerializableImmutableList<String>?, val visibility: TileSchema.Visibility, val widthVisibility: AdaptiveVisibilityTileSchema.WidthVisibility, val heightVisibility: AdaptiveVisibilityTileSchema.HeightVisibility) : TileSchema

Conditionally renders tiles based on the current window size class, read from currentWindowAdaptiveInfoV2(). The children are composed only when both widthVisibility and heightVisibility are satisfied; otherwise nothing is emitted at all — the children are not composed, not merely hidden.

Breakpoint comparison: the current window is ranked against the Material window size class bounds (width: Compact < Medium < Expanded < Large < ExtraLarge; height: Compact < Medium < Expanded). WidthVisibility.VisibleFrom / HeightVisibility.VisibleFrom are satisfied when the current rank is above the given breakpoint (exclusive), so VisibleFrom(Medium) shows from Expanded upwards. WidthVisibility.VisibleUntil / HeightVisibility.VisibleUntil are satisfied when the current rank is at or below the given breakpoint (inclusive), so VisibleUntil(Medium) covers Compact and Medium.

Triggers dispatched:

OnDisplayEventTrigger — fired once when the tile enters composition (keyed by tile id), regardless of whether the breakpoints are satisfied.
OnWidthBreakpointSatisfiedEventTrigger / OnWidthBreakpointNotSatisfiedEventTrigger — fired on first composition and on every change of the width condition.
OnHeightBreakpointSatisfiedEventTrigger / OnHeightBreakpointNotSatisfiedEventTrigger — fired on first composition and on every change of the height condition.

The width and height triggers are independent: one may report "satisfied" while the other reports "not satisfied", and in that case the children still stay hidden.

Notes: when both conditions hold, the children are hosted in a Box carrying style and visibility, so they are stacked rather than emitted into the parent's scope.