Automation roots: same_file doesn't open a path on another computer, native NT link targets and names Windows trims are refused, and the docs say network paths are refused
After a zoom step's preview the render thread only checked once, right away,
for a newer request, then started the full render. That render can't be
stopped, so on a heavy page every later step of a held zoom waited for it
(110-520 ms per render on a 9,000-layer page with images and shadows).
It now waits like the browser worker does: SETTLE_MS, or the last full
render's time when that's shorter. Pans and edits have no preview and are
refined straight away as before.
craft_fig_src() ran `cargo metadata --offline` with no platform filter.
Cargo then needs every target's packages in its cache, and a cache that
holds only what a host build fetched lacks iOS-only crates such as
accesskit_ios, so the nightly FreeBSD job failed. Ask the same cargo for
its host triple (`cargo -vV`) and pass it as `--filter-platform`.
* M9: page.setOpening sets the page a shared file opens on, for everyone who joins (#1817)
A file on a figcraft-server opened on the page current at publish time, with no way to change it:
`DocProp::CurrentPage` was synced but nothing wrote it (`page.select` is each viewer's own page,
only a local save stamps the document). `page.setOpening {id?}` writes `doc.current_page` as a
document edit: one undo step, a synced change in a live session, so every later join opens on it;
the current page when none is named; a divider or a layer refused; nobody's own page moves. The
pages list's context menu gets "Set as opening page". Docs: mcp.md, collaboration-parity.md.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M9: the pages menu's new string is in the English catalog (#1817)
The gate's i18n test wants every tr() key in locales/en.toml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity doc states the default when no opening page is set (#1972 issue)
With none set, a file opens on its saved current page, not the first page, and a link cannot name a page, so the row is partial.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: one sharing row, and the spotlight exception on the opening-page row (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity row states where the joiner's page comes from (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: a no-op set adds no step, deleting the opening page falls back, and the tests cover junk ids, refusals, undo and the menu item (#1817)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M5: the chosen opening page is saved with the file and opens it for everyone (#1817)
The opening-page flag now lives on the page node (NodeKind::Page opening), so it syncs
through the existing node kind. Saving writes the flagged page as current_page instead of
the page the saver was viewing. A duplicated page does not copy the flag, and deleting the
page removes it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* M8: Duplicate repeats the copy's rotation as well as its move, and forgets the step on a deselect (#2293)
Duplicate remembered only the shift of the copies' bounds corner, so a turned copy repeated an arbitrary offset and no rotation. The step is now the move of the copies' centre in the page frame plus the turn each copy has over its source, applied to the new copies about their own centre (one layer) or their shared centre (several). Size is not stepped; a resized copy repeats its move, not its growth. Measured in Figma's web app on 2026-11-12. The step was already dropped when the selection changes to anything but the copies (clean_selection), and a test now pins that.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 queued; Opus 5.5 briefed; Sonnet 5.5 measured and wrote at medium
* M8: the duplicate step ignores turns in place, size changes and flips (#2293)
The move of the step is now measured per pair, as each copy's own centre minus its source's, less the shift a size change gives that centre (taken in the source's frame), averaged over the pairs. A turn about a layer's own centre, uneven layers and a widened-then-turned copy no longer record a move. A copy whose flip state differs from its source's repeats no turn, since flips were not measured.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 queued; Opus 5.5 briefed; Sonnet 5.5 measured and wrote at medium
* M8: a turn of several copies together is not counted as a move in the duplicate step (#2293)
Duplicated::step took the mean of the per-pair centre moves, so a Rotate on several uneven layers (turned together about the selection centre) read as an extra move and the next Duplicate applied it. The step now also tries the reading where the copies were turned together about the sources' bounds centre, and uses it when every copy fits it and the in-place reading does not fit. Two tests cover a turn together and a move plus turn together.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
* M8: the duplicate step reads a turn about the rotation handle's centre, and a resize after a turn, as no move (#2293)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
* M8: the duplicate step turns several layers about their handle box's centre, with no pivot inferred (#2293)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 briefed; Sonnet 5.5 wrote at medium
* Docs: repair a row the earlier merges garbled (Alt-drag duplicate)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
On revert, fired-delay keys are kept only for layers the restored document has: a layer only the hover variant had is gone again, and its id may be issued anew by the next hover. Test a_hover_variants_own_layer_leaves_no_fired_key_after_the_revert (red before: a key for the missing NodeId(8) stayed); present 106 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A fired-delay key is (node, index), and inside an instance the index belongs to the variant shown. On revert, keys that fired during the temporary change inside an instance it changed the variant of are dropped (they name the hover variant's interactions); the snapshot's keys come back and the other new ones stay. Test a_delay_fired_on_a_hover_variant_does_not_block_the_restored_variants_delay (red before: A's runs left 0, right 1); present 105 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The while-hovering / while-pressing snapshot also keeps the fired After delays, and the revert puts back the ones the temporary variant change cleared (keeping any that fired during it), so a delay that already ran on the variant doesn't run again. When an edit in the editor replaces the presented document, the run-time swap times are cleared with the rest of that state.
Tests: a_hover_variant_that_reverts_does_not_rerun_a_fired_delay (red before: count left 2, right 1) and an_edit_while_presenting_drops_the_swap_times (red before: left Some(0), right Some(1)); present 104 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The swap times now travel with the while-hovering / while-pressing snapshot, so reverting a hover's variant change restores them and the variant shown again fires on its own deadline. Test a_hover_variant_that_reverts_keeps_the_after_delay_deadline (red before: left Some(0), right Some(2) at 1.3 s); present 102 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Change to swapped the instance's variant in place, so the next variant's After delay
kept the instance's node id and was already recorded as fired: the chain stopped
after one step. The swap now clears the fired keys inside the instance and records
when it happened; next_delay counts a timer from the later of the screen's arrival
and that swap.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
Both moves had names of the same length, so which one ran first came
from the order of the variables. The first one now has a longer name,
which the longest-first order always moves first, so the second one
always collides after a move that has to be undone.
The collision test's two moves had names of the same length, so the
first one already collided and nothing was left to undo. With the
existing name on the second move, the first moves, the second collides,
and the test checks that the batch puts the first one back.