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.
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.
boundVariables.individualStrokeWeights was skipped with a warning, so a 1 px bottom divider bound to a variable came across as a plain number. Each side now binds strokeTopWeight ... strokeLeftWeight, read from the live API's BORDER_TOP_WEIGHT ... keys or the published spec's top ... keys.
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
exchange::libraries kept the fetches' answers until every job had run, and
Driver::follow handed them over only at Next::Done, so a library that had
answered waited behind later libraries and reports that connected or timed out.
A new Next::Tell gives the UI its events, then goes on; libraries ends each
fetch with it, before connecting for the next job, as the desktop's
library_background does.
Test: exchange_tests::a_library_check_hands_each_fetch_over_as_it_comes (the
first library is in the inbox while a later report's server never answers).
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.
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