Repository navigation
0.18.6
A mockup's frames must hold each size's regions, and the drawing shows either
side of each switch the project records.
Fixed
- The gate checks what a mockup's frames hold, not only that they exist.
0.18.5 required a frame per size; a frame can still be empty, or hold the
desktop composition narrower. The procedure's self-check, "go down the spec's
regions:and find each one in that frame", was prose only. Now each size's
regions must be labelled in its frame: by name where the spec gives a short
one (nav, orh1: "Versions"), and by count where it writes a description,
so wording never trips it. - A mockup draws either side of each switch the project records. The probe
has measured one pixel either side of every--breakpoint-*since 0.18.0, but
the drawing the owner approves showed only the four sizes; jig-site's header
changes at 540, between phone and tablet, and no frame showed 539 beside 540.
A new spec field,switches:, names the switches a page crosses (noneif it
crosses none); absent, the mockup draws every one. - A spec's
indexable:reads past a YAML comment. The spec template itself
writesindexable: true # from the mode ...; a spec that copied it was
reported unreadable.