A dimmed row's hover painted the lighter hover fill, which left its dim
text at 4.3:1 in the default Charcoal theme and at 4.1:1 in Classic Dark,
under the 4.5:1 the dim colour is drawn for. A dimmed row can't be dragged
in again, so its hover is now a recess in the panel's darker fill, which
keeps 4.5:1 or better in every colour scheme and brightness.
The docs now give the measured range: 4.5:1 or better on the panel in every
Modern brightness and in Classic's lightest and darkest settings, 5.4:1 in
the default theme, and Classic's own dim text at 3.55:1 at its middle-dark
brightness, which the drawer draws as that palette does.
Tests: a_hovered_dimmed_row_stays_readable (new) checks the hover fill and
its contrast in both schemes and all four brightnesses;
tools_in_the_toolbar_are_dimmed_in_the_drawer now covers every palette too.
* .ai import: blank area type keeps its frame, blank point type quiet
A text object whose story is blank (nothing but spaces and line ends)
was never made (`Story::node`), so its slot
was left empty and counted in the note "text objects on hidden layers
or hidden objects couldn't be read", shown or not.
A slot of a blank story that neither the text document nor the page
fills is now settled after the page is matched, so the page's type
still takes it where the page has some for it alone:
- Blank area type and type on a path come in as a text object that
keeps its frame or path and draws nothing (`Story::blank_frame_node`),
as VectorCraft's Type tool keeps an empty frame (#85, #154). That
covers a frame the page's spare type went past (`Merged`) too. It is
kept without being weighed against the page, and so are the later
frames of its thread.
- Blank point type draws nothing and has nothing to keep, so it is left
out without a note, as the Type tool discards empty point type.
- A blank slot takes the page's type left over only when no other open
slot can (`readable_first`), so it no longer takes another object's
type by painting order.
- A blank story's thread isn't held against an unread object that takes
one of its frames, and a thread lists only the frames still there.
Its frames are still threaded type to warps and envelopes, which
never take the place of such a frame.
The note for text objects still left out no longer says they are
hidden: "text objects whose type couldn't be read from the file's text
document or its page are left out".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* .ai import: a blank frame an unread object leaves alone isn't threaded type
When an unread object takes one frame of a blank story's two-frame
thread with it, the other frame is no longer threaded in the document,
but warps and envelopes still treated it as threaded type and so never
weighed it against its look. They now get the frames of the threads
actually kept.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Test: the lone blank frame in a warp comes in as its look, no text left
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* SVG export: preserve document unit in viewBox and width/height (#864)
When exporting SVG documents with physical units (mm, cm, in, pc), emit
the physical unit suffix on the root <svg width=... height=...>
attributes while keeping viewBox numbers and inner coordinates in 1:1 points
per SVG 1.1 coords §7.10. This avoids the 75% scaling mismatch when opening
drawings in external tools such as Inkscape or LightBurn, and preserves
the document unit setting across save/open round trips. Unitless documents
(points, pixels) continue to emit unitless dimensions.
Tested via export_physical_units_writes_unit_suffixes in vectorcraft-svg
and full round-trip svg_round_trip_preserves_document_units in vectorcraft-engine.
Ran cargo xtask ci (fmt, clippy, tests, xtask gates).
* SVG export: preserve nonzero width and viewBox on extreme small dimensions
The PDF writer dates each file and makes its IDs from the clock, so two
sheet exports on either side of a second boundary differed there and the
test failed on main's coverage run.
Each <textPath> with an href walked the whole document to find the element it names, so a file with many texts on paths took time proportional to the number of texts times the number of elements. The importer now builds a map of element ids at the first such lookup, keeping the first element in document order for each id, and looks each href up there. Files whose texts name no element do not build the map. The imported document is the same: a test compares the whole document and warnings with the per-id walk, including duplicate, missing and unusable ids.
Clicking between app windows (floating panels and the canvas) passes through one frame where none of them has focus. The palette levels counted the app inactive on that frame and lowered every floating panel's OS window. The panels flickered, could end up disappearing behind the main window until the next repaint, and a click on one panel's bar could hand the keyboard to another.
The app now counts as inactive once none of its windows has had focus for 0.25 s, counted from the first frame that saw none. craft-ui's docking waits as long.
Fixes#6986
- The French script error line now has the catalog's no-break spaces before its colons.
- es.tsv drops the old file.info control character row a merge brought back.
Two PRs merged tonight each added the same row, so bundled_catalogs_are_consistent fails on main
(gu: duplicate "" "Panel"). Both rows have the same translation.
Conflicts in docs only (status lines, changelog rows and table rows):
main's entries and this branch's are both kept, each once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>