In a right-to-left UI language the rows inside the panels run from the
right as well: the shared Design panel row (right::block), section
headers, tight_end, sub-labels, checkboxes, radios, disclosures and the
selection header, and the layers and pages lists (indent, disclosure,
icon and name from the right, eye and padlock on the left). Names and
rename fields align to their start.
Hand-placed layouts stay written left to right and are mirrored inside
their row with widgets::flip_x / flip_rect, so an English window takes
the same code path unchanged. Inside a control nothing turns round.
A layers list made wider than the panel by a long name (#1904)
mirrors across its whole width, so it starts scrolled to its right
end, where its rows start (stick_to_right, with a scroll state per
direction so a language switch doesn't leave it at the left end).
The Assets panel, version history, Dev Mode's layouts, the colour
picker, the toolbar, the tab bar and the home screen stay left to right.
Gap 5 had two copies of its "Missing" paragraph, left by merges: one
now.
Publishing keeps the variables its styles bind and where its copies of other libraries' assets came
from; importing files such a copy under that library when the file links it.
Without a device, a frame taller than the window scrolled its content and then panned whole, taking
fixed and sticky layers off the top. A frame with them now takes the window as its screen.
From review: the asset list follows the layers placed in the tree, so a
smaller tree (maxNodes, or the MCP tool's retry for maxBytes) means a smaller
list, and `truncated.assetsLeftOut` counts the rest; following aliases reports
`truncated.variables` when it stops at its budget with variables still to
read; and a font is checked with figcraft_text::has_family by its trimmed name,
as the missing-fonts list does, so a family stored with outer spaces isn't
taken for installed. A regression test for each fails without its fix.
From review: the variables a style binds and those an alias or colour
calculation reads are joined too, followed to any depth; fonts come from the
text layers placed in the tree, so a second target's font isn't lost to a
separate walk's budget; and a malformed `id` or `ids` entry is an error
instead of reading the selection or dropping the entry. A regression test for
each fails without its fix.
inspect.designContext and the MCP tool design_context read the selection (or
ids, or a scope) in one call. Each layer keeps apart the values the designer
set (explicit), those layout or the file worked out (derived) and those with no
direct CSS equivalent (unsupported, with the reason). The variables (every
mode's stored and resolved value), styles, components, fonts and assets the
tree uses are joined once, and `missing` says what the design doesn't specify.
A connected instance gives its code snippet instead of its layers. Large trees
are capped and say so, and the MCP tool asks for fewer layers until the result
fits the client.
A fill-only text was left as it was: Outline stroke skipped every layer
without a visible stroke. A text now flattens in place into a vector of
its glyphs, filled as the text was and keeping its colour style,
constraints, visibility and lock; a text with no glyphs stays.
A press on a layer inside a selected one now drags the selection, and a click
without a drag selects that layer (also in Dev Mode and for a single selection),
as in Figma. Cmd/Ctrl, Shift and layers outside the selection are unchanged.
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
transform.nudge applied the step in the parent's local space, so Down inside a frame
rotated 90 degrees moved the layer sideways. The step is now turned into the parent's
space first (falling back to the plain step if the parent's transform is not invertible).
Auto layout children are unchanged.
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
Applying a style or variable, or copying or duplicating content that uses it,
inserts it; the Detach button detaches it; an instance counts as its component
alone. Show usage and library.usage give them over the chosen period.
A property added to a set goes to all its variants (component.addProperty), but
Combine as variants kept each component's own definitions, so a property made
on one component before combining was missing from the others: their layers
couldn't be bound to it ("the component has no property") and an instance
switched to one of them dropped its value. make_variant_set now gives every
variant the properties any of them has (share_props, through the give_prop step
addProperty uses too); a variant with a property of that name keeps its own.
Tests: variant_shared_props_tests.
Cmd/Ctrl+V with one layer inside a frame selected pasted onto the page on top of the frame. It now pastes into the layer's parent just above it, in an auto layout frame the item after it.
Page-level layers, several layers, instance children, board atoms, component sets and copied components keep today's behaviour.
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
In vector edit mode, align.* and distribute.* act on the selected
points instead of moving the whole vector. The Design panel shows the
alignment row, and the existing shortcuts apply to those points.
Closes#2109.
In a hugging parent, Fill on the other axis follows the line the way
Figma does, instead of forcing the parent Fixed. This also covers item 2
of #2090 on both axes: a hugging main that becomes Fixed is followed by
its instances' roots.
Fixes#2091 item 3. Fixes#2034. Fixes item 2 of #2090.
Resolve ROADMAP.md and docs/localization-parity.md by keeping main's
newer log entries and the #1902 Noto Sans Arabic default-web-font notes.
Signed-off-by: FredApps <153173854+FredApps@users.noreply.github.com>
A text field that isn't being edited painted its whole value clipped to the field, so the variant value "Down left" read "Down lef". It now paints the value shortened with an ellipsis to fit, and hovering shows the whole value (not for a secret field). Editing and screen readers keep the whole value.
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
A layer stored its vertical text alignment, text case, paragraph spacing and
indent, OpenType features, start and end caps, a frame's variable modes, which
component property controls a field, and whether a nested instance is exposed,
but node.get and document.inspect left them out. They are reported now, under
the names node.set takes so a value read can be written back, and only when
they aren't the default.
The browser's requests to a server now open library and plugin directory
connections, so the panels work there as on the desktop. A plugin installed in
the browser lasts as long as the page.