Expand description
Paged media: the FragmentationContext (continuous vs. paged) and page margins.
The primitive types live in azul_core::paged; re-exported here so existing
azul_layout::paged::* / crate::paged::* paths keep resolving.
Paged-media primitives: the FragmentationContext (continuous vs. paged) and
PageMargins. The pagination/slicing logic lives in azul_layout::solver3.
Paged media layout primitives.
Provides the [FragmentationContext] that the layout solver threads through to
distinguish continuous (screen) from paged (print) media.
For continuous media (screens), content flows into a single infinitely tall
container. For paged media (print), content is laid out on a continuous canvas
and afterwards sliced into fixed-size pages by the display-list slicer
(paginate_display_list_with_slicer_and_breaks in azul_layout::solver3::display_list).
This lets the layout engine make break decisions while respecting CSS properties
like break-before, break-after, and break-inside.
Page decoration (headers, footers, margin boxes, counters) lives in
azul_layout::solver3::pagination.
Structs§
- Page
Margins - Page margins in points.
Enums§
- Fragmentation
Context - Selects how content is fragmented during layout.