Pin craft-ui to c4b8405d, which adds a top edge and the canvas-side top
corner to icon-strip flyouts and saves the moved top per group. Accept
its new MoveFlyoutTop docking action, and restore the saved top when a
group returns to its place. A docking regression checks the cursors, an
upward top-edge and free-corner drag with the bottom and icon-column edge
fixed, and the top after reopening and in a saved layout.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Codex <codex@openai.com>
The docs, comments and PROVENANCE.md rows R45 to R48 name clipping
containers by what they do, and cite the sample files without a vendor
prefix in their names.
View > Proof Setup > Working CMYK simulates the working CMYK space of
Color Settings in Proof Colors and Separations Preview, also in a
document assigned another CMYK profile. The active context keeps the
working context beside the assigned profiles, and the proof table cache
key includes the working settings, so a change of the working CMYK space
shows in the next proof.
A drawn ellipse whose record ends before its two angles came in as a
whole ellipse with no warning; it is now left out as damage. The file
format table now says that version 3 envelopes are not applied and the
objects under them are kept, and gives one count of the formats opened.
PROVENANCE.md, the crate README and docs/mcp.md now say which parts of
versions 1 to 4 public specifications cover.
The crate's integration tests move to tests/it, one module per area,
built as a single test binary as the other crates' are. The file format
table now lists clipping containers, fills and outlines taken from the object's
style, and the lenses warning.
A drawn outline of width 0 became a stroke of width 0, which the
renderer does not draw. It now becomes a 0.25 pt stroke, the width PDF
import gives a line width of 0.
Bit 0x10 of an outline's line type puts the outline behind the fill, so
that a filled shape shows only its outer half. The reader now reports
it, and the importer paints such a stroke before the fill. A clipping
container's outline behind its fill becomes a stroke of its own below
the clipping group, the two grouped together, since a clipping path's
stroke paints over the clipped objects. PROVENANCE.md row R49 gives the
sample files.
With automation read roots in force, document.json returned each entry of
svg_scripts unchanged, so a JavaScript file linked from outside the read
roots kept its full path in the reply. The reply copy now names such a
file by its file name alone. An entry given as a URL is kept, and the
stored document is not changed.
- object.expand.info reports no gradient or fill to expand for a
gradient that repeats in more runs across its box than are written,
matching object.expand, which leaves it a gradient. For a path that a
painting live effect draws, it measures each piece the effect returns.
- CSS writes a repeating gradient's stop positions, and a repeating
radial gradient's radius, with enough decimals that their rounding
adds up to at most a hundredth of a period across the box (at least
four for positions and three for the radius).
- docs/mcp.md says that sharp steps and swatch-linked stops are the last
to be left out rather than always kept, and that the CSS conic limit
counts stops before midpoints and Perceptual curves add more.
A stroke at an opacity of 0 draws nothing, so its brush is no longer
listed in the Brushes category, brushNames or brushes. Pattern Objects,
Gradient Objects and Spot Color Objects likewise leave out fills and
strokes at an opacity of 0, and Objects no longer counts objects whose
only such paint is at opacity 0.
An object with a lens or a transparency carries argument 8000. The
reader does not apply it, and the object comes in opaque; the warnings
now say so instead of nothing. PROVENANCE.md row R47 lists the sample
files that carry the argument.
A reply hid a hidden library's absolute path wherever it appeared, also
inside another loaded library's id when the match began after the id's
start. With `/libs/Kit.gpl` hidden, the readable id
`loaded//project/libs/Kit.gpl` came back as `loaded//projectKit.gpl`,
and a request that used it failed.
Each whole readable id in a reply (with or without `loaded/`, or in a
`file:` URL with no host or `localhost`) is now found first, and a
hidden id or path that lies inside it stays. The same path after a
drive or in a URL with another host is still hidden.