mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-14 21:29:34 +00:00
Vance Ingalls
1902fc5866
The lanes hung off the active clip's property lanes, and which clip that is follows the selection. So pressing a lane to select its clip moved the whole subtree into a different clip's element: React remounted every lane, each one lost the hover state that draws its handles, and the breakpoints the pointer was reaching for vanished at the moment of the press. That is the one gesture a read-only lane exists to support — press to select, then edit. They are the row's lanes, so the row mounts them. Their absolute positions resolve against the same relative row either way, so the geometry is unchanged. The wrapper is mounted in both disclosure states, empty while collapsed, for the reason the keyframe lanes are: the caret's aria-controls has to resolve while collapsed too. The caret now names both regions, since a clip's keyframe lanes and the track's automation lanes cannot be one element. TimelinePropertyLanes loses its `footer` prop, which existed only for this.