tree 4a77c29b195310b7e3b7983d1a6f41e3ea62ff7b
parent 0a8499b87a7d722b982d9c444172cab94d8320f2
author philter <hello@rive.app> 1785990624 +0000
committer philter <hello@rive.app> 1785990624 +0000

chore: Reset legacy layout transforms (#13400) 6dec243962
Layouts became transformable in #13033 — rotation/scale now compose on top of the solved slot. Older editors let those properties be written in some edge cases on a LayoutComponent but never read them, so files can carry stale values that suddenly took effect. A stored scale 0 collapses the layout to zero size while keeping its position, which is what the reported file hit.

Fixed on both sides, following the layout-image-fit precedent (c372d0d):

Editor — coreVersion 6 → 7. Files below 7 have non-artboard LayoutComponent rotation/scale/x/y reset to identity on open. Render-preserving: identity reproduces the old translation-only composition. x/y is reset ahead of the composition supporting it so files are already clean when that lands. Artboards are excluded — they extend LayoutComponent, but their x/y is the stage position.

Runtime — riv 7.2 → 7.3. LayoutComponent::import records whether the file predates 7.3 and the composition skips stored transforms for those files, so already-exported .riv files render unchanged and need no re-export. LayoutComponent::clone() carries the flag, since every rendered artboard is an instance built by cloning its objects.

Libraries get the same treatment via LibraryAsset.decode(). A library is flattened into the host's .riv under the host's version stamp, so the runtime gate can't protect it; the reset runs on its internalCore instead — in memory, never journaled or sent to coop, so no republish is needed. The shared routine also closes the same latent gap for the coreVersion 5 image migration, which only ever ran on host files.

Co-authored-by: Philip Chung <philterdesign@gmail.com>