@flemo/core 2.2.0 → 2.2.2

package/dist/morph/morphSide.d.ts

@@ -22,6 +22,12 @@ export interface MorphSide {
     padding: string;
     margin: string;
     paint: Record<string, string>;
+    /** Whether this end is one line of text (see MorphSnapshot.singleLine). */
+    singleLine: boolean;
+    /** This end's first text run height (see MorphSnapshot.textHeight). */
+    textHeight: number | null;
+    /** Where this end's line was actually rendered (see MorphSnapshot.leadOffset). */
+    leadOffset: number | null;
     /**
      * Whether this screen's transition MOVES it — read from the DEFINITION, not
      * from the element: at the moment a flight is staged the arriving screen is
@@ -33,11 +39,4 @@ export interface MorphSide {
     screenDuration: number;
     screenEase: AnimationOptions["ease"];
 }
-/**
- * Where one side of a morph really is, and how long its screen takes.
- *
- * The screen is read from the DOM PROTOCOL — its transition name is an
- * attribute — rather than from a store, so a morph works the same for any
- * binding and needs nothing threaded through from the consumer's tree.
- */
-export declare const resolveMorphSide: (element: HTMLElement, screen: HTMLElement, variant: TransitionVariant) => MorphSide;
+export declare const resolveMorphSide: (element: HTMLElement, owner: HTMLElement | null, variant: TransitionVariant) => MorphSide;

package/dist/morph/pinParts.d.ts

@@ -0,0 +1,27 @@
+/**
+ * A PART IS NOT LAID OUT AT THE SIZES THE BOX PASSES THROUGH.
+ *
+ * A morph's box animates so that the subtree can lay itself out at every size
+ * on the way, which is what makes the artwork and the paired type GROW. A
+ * `<Part>` is the opposite declaration: it is the content that is NOT paired,
+ * that the flight hides and brings back on its own clock, precisely because it
+ * has no business being laid out at a cell's width.
+ *
+ * It was laid out there anyway. The part's own box still rode the growing box,
+ * so a page of copy inside a card re-wrapped the whole way up, and the part is
+ * brought back before the box has finished growing. Measured on the reference
+ * detail, frame by frame: the body copy stood at 147.88px tall for the first
+ * twenty frames of the flight, dropped a line to 126.75px on the twenty-first,
+ * and the facts list and the buy button under it jumped 23.55px up the screen
+ * in that one frame, with the copy already at full opacity.
+ *
+ * So a part is laid out ONCE, at the width it will rest at, and the box's
+ * growth is a clip over it rather than a re-wrap of it. Nothing is lost: the
+ * part is not on glass at those sizes, and where it is on glass the width is
+ * the one it lands at.
+ *
+ * The width alone. A part's HEIGHT is where the growth actually shows through
+ * to the parts below it, and holding that would pin a subtree to a height its
+ * own copy no longer needs.
+ */
+export declare const pinPartWidths: (element: HTMLElement) => (() => void);

package/dist/transition/__tests__/gestureScrub.test.d.ts

@@ -0,0 +1 @@
+export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flemo/core",
-  "version": "2.2.0",
+  "version": "2.2.2",
   "description": "Framework-agnostic primitives for flemo: history, navigation, transitions, task manager.",
   "main": "./dist/index.mjs",
   "module": "./dist/index.mjs",