A tag is centred on its bracket, which is shorter than a line of text, so
the audio tag hung below the ruler and leaves it under a larger text size
(the old ruler clipped its marks to its rect). The tag keeps its place
beside its arm, moved up or down only as far as it takes to stay inside.
The table was sized from its content with only fill columns, so it took
its least width and cut every header. It takes the collection default
(Fill): under the dialog's content-sized body it measures from its content,
never sets the dialog's width and shows across it, its columns sharing that
width; its height stays its rows'. The rows take the collection's cell rects
(`cells`), so File Name, File Path and Status show in their columns.
A content-sized inline container shown in a `Stack` body given its width
passes that width on to its own body: its children measure and show as in
a given column, so a child that fills (a fill-width row, a list, a divider,
a picture, a side-labelled control) takes the width, and the container
takes what its content took. A content-sized mount (dialog, popover, menu),
a row, a grid or a held container stops it, so their bodies stay content
columns and measure as before.
The env carries the fact as `given_column`, set by a `Stack` body that is
not a content column and listed in the measure key's env facts. No pass,
record or measuring run is added.
Panel roots that set `fill_width()` only to span their pane now take the
default: CharacterControls, ParagraphControls, TimecodePanel,
ReorderableSections and BlendIfBar each hold a fill child, and where they
sit in a content column (BlendIfBar in the Layer Style page) the column
around them hugs them either way.
The fill_column trial shows the given column, nesting, a row stopping it,
the hug kept in a popover, and the measuring-run count against a
fill-width column.
The column headers take the small control height at every density, as the old grid's did (size.control.sm). The corner between the headers shows the old's select-all triangle in its end-bottom, in the header text colour.
A merged cell was painted by its first row inside that row's clip, so its text was cut and the rows below showed the grid's surface. The grid paints each merged cell in view over its whole rect, cut to each pane it shows in, with the same cell paint as a row's cells (CellPaint: background, the tint of its flags, gridlines, the app's paint). Its flags come from the grid's selection as the item step sets a row's cells'. Rows skip every cell inside a merge. PaintUi::clipped cuts a PaintUi to a rect, as Draw::clipped cuts a Draw.
Rule::edge and Draw::edge_rule draw a rule along one side of a rect, moved in by half its width, so a row's bottom rule, a cell's gridline or a strip's edge is no longer drawn on the first pixel outside, where the next row's clip or the next cell's fill hides it. List rows (layer dividers, rule), CellGrid gridlines and header edges, tab dividers, the tile grid's pinned band, font cards and ruler strips use it, as do the pane, end-region, title bar, timeline header and outline band rules that offset by hand. CellGrid draws the old's header edges toward the cells, its gridlines in the divider colour, and the selected header's accent bar inside the header.
The strip takes a pointer's depth as padding on each side and paints its colours between, so both pointers show beside the area and nothing paints outside its rect.
A white ring with a dark halo just outside it, so one of the two reads on any colour; filled with the colour it marks on the disc and the gradient line, accent when a gradient stop or end is selected, large for a disc's base colour and a gradient line's ends. PointPicker's ring, the wheel knobs, the ramp cursor, the disc markers and the gradient overlay's stops and ends draw it in place of their own rings.
shell::embed holds install (runtime plus fonts), before_input, logic and
before_ui, and CloseDecision. app::run's Driver calls the same hooks.
runtime::keys::with_window_intents is public: the host's read of the
window-level keys no component took. docs/craft-framework.md 2.2
describes the recipe and what install takes over. A trial drives its
own frame loop through the hooks alone.
A consumer build of the craft facade has no dev-dependencies, so craft-ui's
testing feature is off. access.rs used pass_state outside its testing-only
import, the pass-local services listed the testing-only Elisions, and four
craft-imaging stories modules lacked the screen-testing gate.