@astryxdesign/core 0.7.8-canary.ffd29c5 → 0.7.8

package/dist/motion/android/index.d.ts

@@ -0,0 +1,16 @@
+/**
+ * @file index.ts
+ * @input The domain files of the Android constants table
+ * @output Re-exports `keyboard`
+ * @position Entry of the Android constants table (motion/android). It is
+ *   internal to core, not exported from the package entry point.
+ *
+ * Where a touch presentation follows something Android draws itself, such as
+ * the software keyboard, its numbers come from here with their sources. The
+ * UIKit table does the same for iOS.
+ *
+ * SYNC: When you add a domain file, re-export it here and list it in
+ * /packages/core/src/motion/README.md.
+ */
+export { keyboard } from './keyboard.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/motion/android/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/motion/android/index.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;GAaG;AAEH,OAAO,EAAC,QAAQ,EAAC,MAAM,YAAY,CAAC"}

package/dist/motion/android/index.js

@@ -0,0 +1,18 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file index.ts
+ * @input The domain files of the Android constants table
+ * @output Re-exports `keyboard`
+ * @position Entry of the Android constants table (motion/android). It is
+ *   internal to core, not exported from the package entry point.
+ *
+ * Where a touch presentation follows something Android draws itself, such as
+ * the software keyboard, its numbers come from here with their sources. The
+ * UIKit table does the same for iOS.
+ *
+ * SYNC: When you add a domain file, re-export it here and list it in
+ * /packages/core/src/motion/README.md.
+ */
+
+export { keyboard } from "./keyboard.js";

package/dist/motion/android/keyboard.d.ts

@@ -0,0 +1,83 @@
+/**
+ * @file keyboard.ts
+ * @input None
+ * @output `keyboard`: how the software keyboard moves on Android, in Chrome
+ *   with Gboard, as the page sees it. It holds the slides' durations and
+ *   curves, and when they start against Chrome's report and a blur.
+ * @position The keyboard domain of the Android constants table, read by
+ *   keyboard/keyboardModel.ts. The UIKit table holds iOS's keyboard.
+ *
+ * SYNC: When modified, update /packages/core/src/keyboard/README.md
+ */
+export declare const keyboard: {
+    /**
+     * How long Gboard takes to slide up, in ms: from its first moved frame to
+     * its resting top.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); 20 shows recorded frame by frame: 250 to 282 ms, 18 of
+     *   them 264 to 268 ms, Oct 25 2026
+     */
+    readonly showMs: 267;
+    /**
+     * The curve of Gboard's slide up, cubic-bézier control points: fast out,
+     * a long settle.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); the same 20 shows fit this curve over `showMs` within
+     *   2.4 px rms, Oct 25 2026
+     */
+    readonly showCurve: readonly [0.1, 0, 0, 1];
+    /**
+     * How long after Gboard starts to slide up Chrome's report of it fires, in
+     * ms. A show rides from the report dated back by this, joining the slide
+     * where it is.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); twelve shows: the first frame the page painted after the
+     *   visual viewport's resize came 14 to 35 ms (median 33) after Gboard's
+     *   first moved frame, less the 8 ms an event takes on average to reach
+     *   the screen, Oct 25 2026
+     */
+    readonly showReportLagMs: 25;
+    /**
+     * How long Gboard takes to slide down out of the page, in ms.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); 21 hides recorded frame by frame, from Gboard's first
+     *   moved frame until it leaves the screen: 148 to 153 ms in 20 of them;
+     *   this length with `hideCurve` fits them within 7.7 px rms,
+     *   Oct 25 2026
+     */
+    readonly hideMs: 167;
+    /**
+     * The curve of Gboard's slide down, cubic-bézier control points: a slow
+     * first frame, then fast.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); the same 21 hides, a free fit over `hideMs`, Oct 25 2026
+     */
+    readonly hideCurve: readonly [0.3, 0.1, 0.2, 0.9];
+    /**
+     * How long after the focused field blurs (to nothing that brings up a
+     * keyboard) Gboard starts to slide down, in ms.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); five scripted blurs with a marker the page paints on the
+     *   blur: Gboard's first moved frame came from a frame before the marker
+     *   to 33 ms after it (median 16), Oct 25 2026
+     */
+    readonly hideAfterBlurMs: 16;
+    /**
+     * How long after Gboard starts to slide down Chrome's report of the hide
+     * fires, in ms, measured on blurs. A hide nothing predicts, such as Back,
+     * reuses it, though Chrome can report Back later in the slide.
+     *
+     * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+     *   emulator); twelve scripted blurs: the visual viewport's resize came
+     *   42 to 52 ms after the blur (median 49), less `hideAfterBlurMs`,
+     *   Oct 25 2026
+     */
+    readonly hideReportLagMs: 33;
+};
+//# sourceMappingURL=keyboard.d.ts.map

package/dist/motion/android/keyboard.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"keyboard.d.ts","sourceRoot":"","sources":["../../../src/motion/android/keyboard.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAaH,eAAO,MAAM,QAAQ;IACnB;;;;;;;OAOG;;IAEH;;;;;;;OAOG;;IAEH;;;;;;;;;;OAUG;;IAEH;;;;;;;;OAQG;;IAEH;;;;;;OAMG;;IAEH;;;;;;;;OAQG;;IAEH;;;;;;;;;OASG;;CAEK,CAAC"}

package/dist/motion/android/keyboard.js

@@ -0,0 +1,96 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file keyboard.ts
+ * @input None
+ * @output `keyboard`: how the software keyboard moves on Android, in Chrome
+ *   with Gboard, as the page sees it. It holds the slides' durations and
+ *   curves, and when they start against Chrome's report and a blur.
+ * @position The keyboard domain of the Android constants table, read by
+ *   keyboard/keyboardModel.ts. The UIKit table holds iOS's keyboard.
+ *
+ * SYNC: When modified, update /packages/core/src/keyboard/README.md
+ */
+
+// Chrome reports the keyboard once per slide, through the visual viewport,
+// just after the slide starts, never per frame. Content that rides the
+// keyboard plays these curves from the slide's start, so it moves in step
+// with Gboard. They are Gboard's own motion, with no motion role. The system
+// moves the keyboard on them whatever the page does, so any other curve
+// would leave the content out of step.
+//
+// The values come from the Android 15 emulator with Chromium 158 and Gboard.
+// A screen recording at 540 × 1200 gives Gboard's top in every frame, beside
+// a marker the page paints on each report. Every leaf carries one or more
+// `@source`, and android.test.ts enforces it.
+export const keyboard = {
+  /**
+   * How long Gboard takes to slide up, in ms: from its first moved frame to
+   * its resting top.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); 20 shows recorded frame by frame: 250 to 282 ms, 18 of
+   *   them 264 to 268 ms, Oct 25 2026
+   */
+  showMs: 267,
+  /**
+   * The curve of Gboard's slide up, cubic-bézier control points: fast out,
+   * a long settle.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); the same 20 shows fit this curve over `showMs` within
+   *   2.4 px rms, Oct 25 2026
+   */
+  showCurve: [0.1, 0, 0, 1],
+  /**
+   * How long after Gboard starts to slide up Chrome's report of it fires, in
+   * ms. A show rides from the report dated back by this, joining the slide
+   * where it is.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); twelve shows: the first frame the page painted after the
+   *   visual viewport's resize came 14 to 35 ms (median 33) after Gboard's
+   *   first moved frame, less the 8 ms an event takes on average to reach
+   *   the screen, Oct 25 2026
+   */
+  showReportLagMs: 25,
+  /**
+   * How long Gboard takes to slide down out of the page, in ms.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); 21 hides recorded frame by frame, from Gboard's first
+   *   moved frame until it leaves the screen: 148 to 153 ms in 20 of them;
+   *   this length with `hideCurve` fits them within 7.7 px rms,
+   *   Oct 25 2026
+   */
+  hideMs: 167,
+  /**
+   * The curve of Gboard's slide down, cubic-bézier control points: a slow
+   * first frame, then fast.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); the same 21 hides, a free fit over `hideMs`, Oct 25 2026
+   */
+  hideCurve: [0.3, 0.1, 0.2, 0.9],
+  /**
+   * How long after the focused field blurs (to nothing that brings up a
+   * keyboard) Gboard starts to slide down, in ms.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); five scripted blurs with a marker the page paints on the
+   *   blur: Gboard's first moved frame came from a frame before the marker
+   *   to 33 ms after it (median 16), Oct 25 2026
+   */
+  hideAfterBlurMs: 16,
+  /**
+   * How long after Gboard starts to slide down Chrome's report of the hide
+   * fires, in ms, measured on blurs. A hide nothing predicts, such as Back,
+   * reuses it, though Chrome can report Back later in the slide.
+   *
+   * @source measured: Chromium 158 with Gboard on Android 15 (API 35
+   *   emulator); twelve scripted blurs: the visual viewport's resize came
+   *   42 to 52 ms after the blur (median 49), less `hideAfterBlurMs`,
+   *   Oct 25 2026
+   */
+  hideReportLagMs: 33
+};

package/dist/motion/uikit/datePicker.d.ts

@@ -0,0 +1,58 @@
+/**
+ * @file datePicker.ts
+ * @input Nothing; data only
+ * @output Exports `datePicker`: the rules UIDatePicker adds to its wheels. The
+ *   month/year wheels change the date, the AM/PM column follows the hour, a
+ *   column turns back onto a bound, and a day clamps to its month.
+ * @position The date picker domain of the UIKit constants table
+ *   (motion/uikit), for the date and time touch sheets. Every leaf names its
+ *   source, which uikit.test.ts checks.
+ *
+ * SYNC: When modified, update /packages/core/src/motion/MEASUREMENTS.md and
+ * /packages/core/src/motion/README.md.
+ */
+export declare const datePicker: {
+    readonly calendar: {
+        readonly monthYearWheels: {
+            /**
+             * Turning the month or year wheel changes the picker's date, keeping
+             * the day, and fires `valueChanged`.
+             * @source measured: UIKit lab, iOS 26.2 simulator, `.date` `.inline`,
+             *   October 15 → May 15 after the month wheel's fling, with a
+             *   `valueChanged` carrying May 15, Oct 23 2026
+             */
+            readonly changesDate: true;
+        };
+    };
+    readonly wheels: {
+        /**
+         * In 12-hour time the AM/PM column follows the hour. Turning the hour from
+         * 11 to 12 turns the time from AM to PM, and back. From 12 to 1 it keeps
+         * the half of the day.
+         * @source measured: UIKit lab, iOS 26.2 simulator, `.time` `.wheels`,
+         *   en_US: 11:58 AM, hour wheel +1 row → `valueChanged` 12:58 PM; then
+         *   the minute wheel's +4 rows carried the hour from 12 to 1 → 1:02 PM,
+         *   Oct 23 2026
+         */
+        readonly meridiemFollowsHour: true;
+        /**
+         * A column that comes to rest past `minimumDate` or `maximumDate` turns
+         * back onto the bound. Its `valueChanged` already carries the bound. For
+         * example, with bounds 9:00–17:00, the hour of 10:00 dragged to 7 reads
+         * 9:00 at rest. The hour column then turns 64 pt, two rows, back to 9.
+         * @source measured: UIKit lab, iOS 26.2 simulator, `.time` `.wheels`
+         *   with bounds 9:00–17:00 and `minuteInterval` 15, per-frame hour
+         *   offsets after the rest (0.4, 2, 7.4, 16, 26.4, 37.7, 48.3, 56.7,
+         *   62, 64 pt at 33 ms steps) and the `valueChanged` time, Oct 23 2026
+         */
+        readonly restPastBound: "turnToBound";
+        /**
+         * In `.date` wheels a day the month does not have clamps to the month's
+         * last day (January 30, month +1 → February 28).
+         * @source measured: UIKit lab, iOS 26.2 simulator, `.date` `.wheels`
+         *   with bounds Jun 1 2026 – Mar 15 2027, Oct 23 2026
+         */
+        readonly dayClampsToMonth: true;
+    };
+};
+//# sourceMappingURL=datePicker.d.ts.map

package/dist/motion/uikit/datePicker.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"datePicker.d.ts","sourceRoot":"","sources":["../../../src/motion/uikit/datePicker.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;GAYG;AAEH,eAAO,MAAM,UAAU;;;YAGjB;;;;;;eAMG;;;;;QAKL;;;;;;;;WAQG;;QAEH;;;;;;;;;WASG;;QAEH;;;;;WAKG;;;CAGG,CAAC"}

package/dist/motion/uikit/datePicker.js

@@ -0,0 +1,60 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file datePicker.ts
+ * @input Nothing; data only
+ * @output Exports `datePicker`: the rules UIDatePicker adds to its wheels. The
+ *   month/year wheels change the date, the AM/PM column follows the hour, a
+ *   column turns back onto a bound, and a day clamps to its month.
+ * @position The date picker domain of the UIKit constants table
+ *   (motion/uikit), for the date and time touch sheets. Every leaf names its
+ *   source, which uikit.test.ts checks.
+ *
+ * SYNC: When modified, update /packages/core/src/motion/MEASUREMENTS.md and
+ * /packages/core/src/motion/README.md.
+ */
+
+export const datePicker = {
+  calendar: {
+    monthYearWheels: {
+      /**
+       * Turning the month or year wheel changes the picker's date, keeping
+       * the day, and fires `valueChanged`.
+       * @source measured: UIKit lab, iOS 26.2 simulator, `.date` `.inline`,
+       *   October 15 → May 15 after the month wheel's fling, with a
+       *   `valueChanged` carrying May 15, Oct 23 2026
+       */
+      changesDate: true
+    }
+  },
+  wheels: {
+    /**
+     * In 12-hour time the AM/PM column follows the hour. Turning the hour from
+     * 11 to 12 turns the time from AM to PM, and back. From 12 to 1 it keeps
+     * the half of the day.
+     * @source measured: UIKit lab, iOS 26.2 simulator, `.time` `.wheels`,
+     *   en_US: 11:58 AM, hour wheel +1 row → `valueChanged` 12:58 PM; then
+     *   the minute wheel's +4 rows carried the hour from 12 to 1 → 1:02 PM,
+     *   Oct 23 2026
+     */
+    meridiemFollowsHour: true,
+    /**
+     * A column that comes to rest past `minimumDate` or `maximumDate` turns
+     * back onto the bound. Its `valueChanged` already carries the bound. For
+     * example, with bounds 9:00–17:00, the hour of 10:00 dragged to 7 reads
+     * 9:00 at rest. The hour column then turns 64 pt, two rows, back to 9.
+     * @source measured: UIKit lab, iOS 26.2 simulator, `.time` `.wheels`
+     *   with bounds 9:00–17:00 and `minuteInterval` 15, per-frame hour
+     *   offsets after the rest (0.4, 2, 7.4, 16, 26.4, 37.7, 48.3, 56.7,
+     *   62, 64 pt at 33 ms steps) and the `valueChanged` time, Oct 23 2026
+     */
+    restPastBound: 'turnToBound',
+    /**
+     * In `.date` wheels a day the month does not have clamps to the month's
+     * last day (January 30, month +1 → February 28).
+     * @source measured: UIKit lab, iOS 26.2 simulator, `.date` `.wheels`
+     *   with bounds Jun 1 2026 – Mar 15 2027, Oct 23 2026
+     */
+    dayClampsToMonth: true
+  }
+};

package/dist/motion/uikit/index.d.ts

@@ -3,9 +3,9 @@
  * @input The domain files of the UIKit constants table
  * @output Re-exports `springs` and one constant per spring (`SHEET_PRESENT_SPRING`,
  *   …), `scroll`, `timing`, `navigation`, `picker`, `progressBar`,
- *   `segmentedControl`, the `slider` and switch (`switchControl`) domains, and
- *   the gesture thresholds (one `UIKIT_*` group per recognizer, their union
- *   `UIKIT_GESTURES`, and the haptic tables)
+ *   `segmentedControl`, `datePicker`, `slider` and `switchControl`. It also
+ *   re-exports the gesture thresholds: one `UIKIT_*` group per recognizer,
+ *   their union `UIKIT_GESTURES`, and the haptic tables
  * @position Entry of the UIKit constants table (motion/uikit). Internal to
  *   core: not exported from the package entry point
  *
@@ -18,6 +18,7 @@
  * /packages/core/src/motion/README.md.
  */
 export { HAPTIC_FEEDBACK_KINDS, HAPTIC_VIBRATION_PATTERNS, UIKIT_CLICK, UIKIT_CONTROL, UIKIT_GESTURES, UIKIT_LONG_PRESS, UIKIT_PAN, UIKIT_PINCH, UIKIT_PRESS, UIKIT_ROTATION, UIKIT_SCREEN_EDGE_PAN, UIKIT_SWIPE, UIKIT_TAP, UIKIT_VELOCITY, type GestureConstant, type GestureConstantUnit, type HapticFeedbackKind, } from './gestures.js';
+export { datePicker } from './datePicker.js';
 export { navigation, registerNavigationTable } from './navigation.js';
 export { picker } from './picker.js';
 export { progressBar, registerProgressBarTable } from './progressBar.js';

package/dist/motion/uikit/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/motion/uikit/index.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,OAAO,EACL,qBAAqB,EACrB,yBAAyB,EACzB,WAAW,EACX,aAAa,EACb,cAAc,EACd,gBAAgB,EAChB,SAAS,EACT,WAAW,EACX,WAAW,EACX,cAAc,EACd,qBAAqB,EACrB,WAAW,EACX,SAAS,EACT,cAAc,EACd,KAAK,eAAe,EACpB,KAAK,mBAAmB,EACxB,KAAK,kBAAkB,GACxB,MAAM,YAAY,CAAC;AACpB,OAAO,EAAC,UAAU,EAAE,uBAAuB,EAAC,MAAM,cAAc,CAAC;AACjE,OAAO,EAAC,MAAM,EAAC,MAAM,UAAU,CAAC;AAChC,OAAO,EAAC,WAAW,EAAE,wBAAwB,EAAC,MAAM,eAAe,CAAC;AACpE,OAAO,EAAC,mBAAmB,EAAE,MAAM,EAAC,MAAM,UAAU,CAAC;AACrD,OAAO,EAAC,gBAAgB,EAAC,MAAM,aAAa,CAAC;AAC7C,OAAO,EAAC,MAAM,EAAC,MAAM,UAAU,CAAC;AAChC,OAAO,EACL,2BAA2B,EAC3B,2BAA2B,EAC3B,oBAAoB,EACpB,oBAAoB,EACpB,aAAa,EACb,2BAA2B,EAC3B,wBAAwB,EACxB,yBAAyB,EACzB,oBAAoB,EACpB,eAAe,EACf,sBAAsB,EACtB,eAAe,EACf,iBAAiB,EACjB,gBAAgB,EAChB,0BAA0B,EAC1B,8BAA8B,EAC9B,wCAAwC,EACxC,qBAAqB,EACrB,sBAAsB,EACtB,mBAAmB,EACnB,aAAa,EACb,mBAAmB,EACnB,oBAAoB,EACpB,0BAA0B,EAC1B,oBAAoB,EACpB,yBAAyB,EACzB,mBAAmB,EACnB,oBAAoB,EACpB,oBAAoB,EACpB,wBAAwB,EACxB,mBAAmB,EACnB,kBAAkB,EAClB,oBAAoB,EACpB,OAAO,GACR,MAAM,WAAW,CAAC;AACnB,OAAO,EAAC,aAAa,EAAC,MAAM,UAAU,CAAC;AACvC,OAAO,EAAC,mBAAmB,EAAE,MAAM,EAAC,MAAM,UAAU,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/motion/uikit/index.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,OAAO,EACL,qBAAqB,EACrB,yBAAyB,EACzB,WAAW,EACX,aAAa,EACb,cAAc,EACd,gBAAgB,EAChB,SAAS,EACT,WAAW,EACX,WAAW,EACX,cAAc,EACd,qBAAqB,EACrB,WAAW,EACX,SAAS,EACT,cAAc,EACd,KAAK,eAAe,EACpB,KAAK,mBAAmB,EACxB,KAAK,kBAAkB,GACxB,MAAM,YAAY,CAAC;AACpB,OAAO,EAAC,UAAU,EAAC,MAAM,cAAc,CAAC;AACxC,OAAO,EAAC,UAAU,EAAE,uBAAuB,EAAC,MAAM,cAAc,CAAC;AACjE,OAAO,EAAC,MAAM,EAAC,MAAM,UAAU,CAAC;AAChC,OAAO,EAAC,WAAW,EAAE,wBAAwB,EAAC,MAAM,eAAe,CAAC;AACpE,OAAO,EAAC,mBAAmB,EAAE,MAAM,EAAC,MAAM,UAAU,CAAC;AACrD,OAAO,EAAC,gBAAgB,EAAC,MAAM,aAAa,CAAC;AAC7C,OAAO,EAAC,MAAM,EAAC,MAAM,UAAU,CAAC;AAChC,OAAO,EACL,2BAA2B,EAC3B,2BAA2B,EAC3B,oBAAoB,EACpB,oBAAoB,EACpB,aAAa,EACb,2BAA2B,EAC3B,wBAAwB,EACxB,yBAAyB,EACzB,oBAAoB,EACpB,eAAe,EACf,sBAAsB,EACtB,eAAe,EACf,iBAAiB,EACjB,gBAAgB,EAChB,0BAA0B,EAC1B,8BAA8B,EAC9B,wCAAwC,EACxC,qBAAqB,EACrB,sBAAsB,EACtB,mBAAmB,EACnB,aAAa,EACb,mBAAmB,EACnB,oBAAoB,EACpB,0BAA0B,EAC1B,oBAAoB,EACpB,yBAAyB,EACzB,mBAAmB,EACnB,oBAAoB,EACpB,oBAAoB,EACpB,wBAAwB,EACxB,mBAAmB,EACnB,kBAAkB,EAClB,oBAAoB,EACpB,OAAO,GACR,MAAM,WAAW,CAAC;AACnB,OAAO,EAAC,aAAa,EAAC,MAAM,UAAU,CAAC;AACvC,OAAO,EAAC,mBAAmB,EAAE,MAAM,EAAC,MAAM,UAAU,CAAC"}

package/dist/motion/uikit/index.js

@@ -5,9 +5,9 @@
  * @input The domain files of the UIKit constants table
  * @output Re-exports `springs` and one constant per spring (`SHEET_PRESENT_SPRING`,
  *   …), `scroll`, `timing`, `navigation`, `picker`, `progressBar`,
- *   `segmentedControl`, the `slider` and switch (`switchControl`) domains, and
- *   the gesture thresholds (one `UIKIT_*` group per recognizer, their union
- *   `UIKIT_GESTURES`, and the haptic tables)
+ *   `segmentedControl`, `datePicker`, `slider` and `switchControl`. It also
+ *   re-exports the gesture thresholds: one `UIKIT_*` group per recognizer,
+ *   their union `UIKIT_GESTURES`, and the haptic tables
  * @position Entry of the UIKit constants table (motion/uikit). Internal to
  *   core: not exported from the package entry point
  *
@@ -21,6 +21,7 @@
  */
 
 export { HAPTIC_FEEDBACK_KINDS, HAPTIC_VIBRATION_PATTERNS, UIKIT_CLICK, UIKIT_CONTROL, UIKIT_GESTURES, UIKIT_LONG_PRESS, UIKIT_PAN, UIKIT_PINCH, UIKIT_PRESS, UIKIT_ROTATION, UIKIT_SCREEN_EDGE_PAN, UIKIT_SWIPE, UIKIT_TAP, UIKIT_VELOCITY } from "./gestures.js";
+export { datePicker } from "./datePicker.js";
 export { navigation, registerNavigationTable } from "./navigation.js";
 export { picker } from "./picker.js";
 export { progressBar, registerProgressBarTable } from "./progressBar.js";

package/dist/utils/interactionOverlay.stylex.d.ts

@@ -33,8 +33,9 @@ export declare const pressVars: stylex.VarGroup<Readonly<{
  *
  * `defineConsts`, so the one number is inlined here at build time and is the
  * controller's constant at run time (`PRESS_FADE_MS` in pressGesture.ts):
- * the release animation and the timer that removes the attribute after it
- * cannot drift apart.
+ * the release animation and the controller's clock cannot drift apart. When
+ * that clock runs out, the controller waits for a release animation that a
+ * busy main thread started late, then removes the attribute.
  */
 export declare const pressConsts: {
     /** How long the release takes, in ms. UIKit's deselect clock. */

package/dist/utils/interactionOverlay.stylex.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"interactionOverlay.stylex.d.ts","sourceRoot":"","sources":["../../src/utils/interactionOverlay.stylex.ts"],"names":[],"mappings":"AAMA;;;;;;;;;;;;;;GAcG;AAmCH,OAAO,KAAK,MAAM,MAAM,kBAAkB,CAAC;AAG3C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,SAAS;;WAEpB,CAAC;AAEH;;;;;;;GAOG;AACH,eAAO,MAAM,WAAW;IACtB,iEAAiE;;CAEjE,CAAC;AA8HH,eAAO,MAAM,wBAAwB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA8HnC,CAAC"}
+{"version":3,"file":"interactionOverlay.stylex.d.ts","sourceRoot":"","sources":["../../src/utils/interactionOverlay.stylex.ts"],"names":[],"mappings":"AAMA;;;;;;;;;;;;;;GAcG;AAmCH,OAAO,KAAK,MAAM,MAAM,kBAAkB,CAAC;AAG3C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,SAAS;;WAEpB,CAAC;AAEH;;;;;;;;GAQG;AACH,eAAO,MAAM,WAAW;IACtB,iEAAiE;;CAEjE,CAAC;AA8HH,eAAO,MAAM,wBAAwB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA8HnC,CAAC"}

package/dist/utils/interactionOverlay.stylex.js

@@ -78,8 +78,9 @@ export const pressVars = {
  *
  * `defineConsts`, so the one number is inlined here at build time and is the
  * controller's constant at run time (`PRESS_FADE_MS` in pressGesture.ts):
- * the release animation and the timer that removes the attribute after it
- * cannot drift apart.
+ * the release animation and the controller's clock cannot drift apart. When
+ * that clock runs out, the controller waits for a release animation that a
+ * busy main thread started late, then removes the attribute.
  */
 export const pressConsts = {
   releaseMs: 200

package/dist/utils/layoutViewport.d.ts

@@ -0,0 +1,25 @@
+/**
+ * @file layoutViewport.ts
+ * @input A window: its innerHeight and innerWidth, its visual viewport's
+ *   width and scale, and its document's root box
+ * @output layoutViewportHeight, the layout viewport's height in layout px
+ *   less a classic horizontal scrollbar, and __resetLayoutViewportForTest
+ * @position Internal shared measurement, not re-exported from the utils
+ *   entry. The keyboard module, BottomSheet's keyboard obstruction and any
+ *   layout that sizes against the layout viewport read it.
+ */
+/**
+ * The layout viewport's height, CSS px, in the units of element rects.
+ *
+ * `innerHeight` is the layout viewport's height in most engines. WebKit
+ * reports `innerHeight` and `innerWidth` in the pinch-zoomed visual
+ * viewport's px instead. At a 1.33 zoom of a 402 × 714 layout viewport,
+ * Safari on iOS 26.2 reports 536 and 302. Element rects and the visual
+ * viewport's height times its scale stay in layout px. So, read as is, a zoom
+ * shrinks the layout viewport by the zoom, and the function scales the height
+ * back.
+ */
+export declare function layoutViewportHeight(win: Window): number;
+/** Forgets every measured scrollbar thickness. Tests only. */
+export declare function __resetLayoutViewportForTest(): void;
+//# sourceMappingURL=layoutViewport.d.ts.map

package/dist/utils/layoutViewport.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"layoutViewport.d.ts","sourceRoot":"","sources":["../../src/utils/layoutViewport.ts"],"names":[],"mappings":"AAEA;;;;;;;;;GASG;AAEH;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAmBxD;AAyDD,8DAA8D;AAC9D,wBAAgB,4BAA4B,IAAI,IAAI,CAEnD"}

package/dist/utils/layoutViewport.js

@@ -0,0 +1,102 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file layoutViewport.ts
+ * @input A window: its innerHeight and innerWidth, its visual viewport's
+ *   width and scale, and its document's root box
+ * @output layoutViewportHeight, the layout viewport's height in layout px
+ *   less a classic horizontal scrollbar, and __resetLayoutViewportForTest
+ * @position Internal shared measurement, not re-exported from the utils
+ *   entry. The keyboard module, BottomSheet's keyboard obstruction and any
+ *   layout that sizes against the layout viewport read it.
+ */
+
+/**
+ * The layout viewport's height, CSS px, in the units of element rects.
+ *
+ * `innerHeight` is the layout viewport's height in most engines. WebKit
+ * reports `innerHeight` and `innerWidth` in the pinch-zoomed visual
+ * viewport's px instead. At a 1.33 zoom of a 402 × 714 layout viewport,
+ * Safari on iOS 26.2 reports 536 and 302. Element rects and the visual
+ * viewport's height times its scale stay in layout px. So, read as is, a zoom
+ * shrinks the layout viewport by the zoom, and the function scales the height
+ * back.
+ */
+export function layoutViewportHeight(win) {
+  const viewport = win.visualViewport;
+  const width = viewport?.width ?? 0;
+  if (viewport == null || !(width > 0)) {
+    return win.innerHeight - horizontalScrollbarHeight(win);
+  }
+  const scale = viewport.scale;
+  // Which units `innerWidth` is in tells the two apart without naming an
+  // engine. It is the visual viewport's width where the zoom applies, and
+  // that width times the scale where it does not. `innerWidth` is a whole
+  // number of px against a fractional width, so it never equals either, and
+  // the nearest wins with no tolerance constant. At a scale of 1 the two
+  // widths are equal, so the function takes `innerHeight` as it is. A classic
+  // scrollbar, which `innerWidth` counts, then changes nothing.
+  const fromVisual = Math.abs(win.innerWidth - width);
+  const fromLayout = Math.abs(win.innerWidth - width * scale);
+  const height = fromVisual < fromLayout ? win.innerHeight * scale : win.innerHeight;
+  return height - horizontalScrollbarHeight(win);
+}
+
+/**
+ * The document's classic horizontal scrollbar, CSS px. It is in
+ * `innerHeight` but not in the visual viewport's height. On a desktop page
+ * wider than its window, Chromium's `innerHeight` is 800 for a 785 px visual
+ * viewport. It is the part of `innerHeight` the root's client height leaves
+ * out, up to the thickness of a scrollbar that takes room. Where scrollbars
+ * overlay the content, as on every phone, that thickness is 0. So the room a
+ * hidden toolbar adds to `innerHeight` is never taken for a scrollbar. Chrome
+ * on Android sizes the root to the viewport with its toolbar shown.
+ */
+function horizontalScrollbarHeight(win) {
+  const root = win.document.documentElement;
+  const gap = win.innerHeight - root.clientHeight;
+  if (!(gap > 0) || root.scrollWidth <= root.clientWidth) {
+    return 0;
+  }
+  return Math.min(gap, scrollbarThickness(win.document));
+}
+
+// The scrollbar thickness each document measured, and the device pixel ratio
+// it measured it at. A browser zoom changes the ratio, and with it how many
+// CSS px a classic scrollbar takes. Measuring writes a probe to the document
+// and forces a layout, so it runs once per document and zoom. Every later
+// measurement stays one layout read.
+let thicknesses = new WeakMap();
+
+/** How much room a scrollbar takes from a scrolling box: 0 where overlaid. */
+function scrollbarThickness(doc) {
+  const devicePixelRatio = doc.defaultView?.devicePixelRatio ?? 1;
+  const known = thicknesses.get(doc);
+  if (known != null && known.devicePixelRatio === devicePixelRatio) {
+    return known.thickness;
+  }
+  const thickness = measureScrollbarThickness(doc);
+  thicknesses.set(doc, {
+    devicePixelRatio,
+    thickness
+  });
+  return thickness;
+}
+function measureScrollbarThickness(doc) {
+  const probe = doc.createElement('div');
+  probe.style.position = 'absolute';
+  probe.style.top = '-200px';
+  probe.style.width = '100px';
+  probe.style.height = '100px';
+  probe.style.overflow = 'scroll';
+  probe.style.visibility = 'hidden';
+  (doc.body ?? doc.documentElement).append(probe);
+  const thickness = probe.offsetHeight - probe.clientHeight;
+  probe.remove();
+  return thickness;
+}
+
+/** Forgets every measured scrollbar thickness. Tests only. */
+export function __resetLayoutViewportForTest() {
+  thicknesses = new WeakMap();
+}

package/dist/utils/pressFeedback.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"pressFeedback.d.ts","sourceRoot":"","sources":["../../src/utils/pressFeedback.ts"],"names":[],"mappings":"AAkDA;;;;;;GAMG;AACH,eAAO,MAAM,mBAAmB,0BAA0B,CAAC;AAE3D;;;;GAIG;AACH,eAAO,MAAM,iBAAiB,sBAAsB,CAAC;AAErD,qDAAqD;AACrD,eAAO,MAAM,cAAc,EAAE;IAAC,QAAQ,CAAC,CAAC,mBAAmB,CAAC,EAAE,EAAE,CAAA;CAE/D,CAAC;AAEF;;;;;GAKG;AACH,eAAO,MAAM,uBAAuB,OAAO,CAAC;AAyE5C;;;;GAIG;AACH,wBAAgB,WAAW,CAAC,OAAO,EAAE,OAAO,GAAG,MAAM,CAUpD;AAqjBD;;;;;;;;;;;;GAYG;AACH,wBAAgB,oBAAoB,IAAI,MAAM,IAAI,CA0BjD"}
+{"version":3,"file":"pressFeedback.d.ts","sourceRoot":"","sources":["../../src/utils/pressFeedback.ts"],"names":[],"mappings":"AAkDA;;;;;;GAMG;AACH,eAAO,MAAM,mBAAmB,0BAA0B,CAAC;AAE3D;;;;GAIG;AACH,eAAO,MAAM,iBAAiB,sBAAsB,CAAC;AAErD,qDAAqD;AACrD,eAAO,MAAM,cAAc,EAAE;IAAC,QAAQ,CAAC,CAAC,mBAAmB,CAAC,EAAE,EAAE,CAAA;CAE/D,CAAC;AAEF;;;;;GAKG;AACH,eAAO,MAAM,uBAAuB,OAAO,CAAC;AA0E5C;;;;GAIG;AACH,wBAAgB,WAAW,CAAC,OAAO,EAAE,OAAO,GAAG,MAAM,CAUpD;AAkoBD;;;;;;;;;;;;GAYG;AACH,wBAAgB,oBAAoB,IAAI,MAAM,IAAI,CA0BjD"}