mirror of
https://github.com/penpot/penpot.git
synced 2026-11-21 01:22:01 +00:00
A copy inside a plain board, such as a main, follows the board's resizes through its constraints. That resize is not an override: the user did not set the size. The next sync of the copy's own component then gave it the component's size, undoing the constraint: a copy scaled to 80 px inside an 80 px main went back to 100 px and overflowed it. When syncing a copy head whose parent is a plain board, keep the dimensions its constraints tie to that board (scale or left-right horizontally, scale or top-bottom vertically); its other attributes still sync. The main is placed at those dimensions first, so the copy's children follow through their constraints. A second re-run of the seed-20261101 library property found this; it also fails on earlier commits. The regression fails before the fix (100 px after a fill edit of the component) and passes after it: the copy stays 80 px tall, takes the new fill, keeps the component's width and gets no geometry override. Full common passes lint, JVM, JavaScript and formatting: JVM 2078 tests / 33886 assertions; JavaScript 2014 / 32497. All six component properties pass 40 programs each at seed 712 in both runtimes. Compare lower-quantile milliseconds with the saved baseline; keep that baseline unchanged. The machine/JVM warning makes ratios rough. No world is flagged. World Baseline Now Ratio Main into 10 copies 1.790 0.895 0.50 Main into 100 copies 15.415 9.268 0.60 Main into 1000 copies 153.086 91.733 0.60 Three nesting levels 35.215 18.542 0.53 Dependency chain 68.931 37.663 0.55 Library update 83.083 44.259 0.53 Many plain shapes 4.837 2.206 0.46 Variant switch 32.052 20.658 0.64 AI-assisted-by: claude-opus-5-5