@seatlayer/js 0.85.2 → 0.86.1

package/dist/index.d.cts

@@ -3921,6 +3921,14 @@ declare class SeatPicker implements GaPromptPicker {
     private buildArenaChrome;
     /** Keep the camera's fitted viewport clear of measured multi-floor chrome. */
     /** @internal */ syncArenaViewportInsets(): void;
+    /**
+     * The phone zoom column is a SOFT bottom clearance instead (owner, 2026-09-07
+     * capture: the discs sat on the Cm/Cn blocks with a third of the map above
+     * the venue empty): a venue short enough to fit above the column is centred
+     * in that band, a taller one keeps the whole map. Duck-typed for an older
+     * @seatlayer/core without the hook.
+     */
+    /** @internal */ syncFitClearance(): void;
     /** Reflect the engine's current LOD rung onto the pill group. */
     /** @internal */ syncRung(): void;
     /**
@@ -3933,32 +3941,32 @@ declare class SeatPicker implements GaPromptPicker {
      * carries "+" and "−" and never shows the fit disc (CSS, see pickerStyles),
      * but "−" answers to the same reading there.
      *
-     * GONE, NOT DIMMED (owner call 2026-09-06, from real-iPhone captures, and
-     * the second time this had been asked for). The rationale before that was
-     * that a control which stays put and plainly cannot be pressed says "you are
-     * already looking at everything" without moving the target. It did not: two
-     * greyed discs at the arrival view were read as a broken map, and they are
-     * the FIRST thing a buyer sees, before they have any model of the ladder
-     * they are at the top of. So "−", the fit disc and "+" all left the column
-     * at their limits, and returned the moment there was a step to take.
-     *
-     * + AND − DO NOT LEAVE ANY MORE (owner call 2026-09-07, real-iPhone
-     * capture): "+ and − must always be in the same place." With three discs
-     * free to come and go, a corner-anchored column that grows upward reshuffled
-     * the two discs a buyer actually aims at — "sometimes + shows at the bottom
-     * and − at the very top and two in between". A control that never moves is
-     * worth more than a column with no dim in it, so this supersedes the
-     * 2026-09-06 call FOR "+" AND "−": they hold fixed adjacent slots (+ above
-     * −, see the `order` rules in pickerStyles) and go `disabled` at their
-     * limits, which the `.sl-zoom>button:disabled` rule dims. Both layouts —
-     * wide hid "−" at the venue fit too, which moved "+" there as well.
-     *
-     * THE FIT DISC STILL LEAVES, and it is the top disc on narrow now, so its
-     * departure moves nothing below it. `hidden`, and a CSS rule loud enough to
-     * beat the narrow `display:flex` on it. display:none, so the column closes
-     * the gap rather than leaving the ♿ floating a disc off the corner — which
-     * is also why the ♿ menu is re-bounded afterwards: its panel is clamped to
-     * the room above a button that may have just moved.
+     * THE HISTORY, BECAUSE IT WENT BOTH WAYS TWICE. Originally every disc dimmed
+     * at its limit. On 2026-09-06, from real-iPhone captures, they LEFT instead:
+     * two greyed discs at the arrival view were read as a broken map, and they
+     * are the FIRST thing a buyer sees, before they have any model of the ladder
+     * they are at the top of. Then on 2026-09-07 (morning) "+" and "−" came back
+     * as fixed slots that vanished in place, because a corner-anchored column
+     * that grows upward reshuffled the two discs a buyer actually aims at —
+     * "sometimes + shows at the bottom and − at the very top and two in between".
+     *
+     * A DISC AT ITS LIMIT DIMS IN PLACE AND NEVER LEAVES (owner call 2026-09-07,
+     * evening, off a phone capture of the buyer picker): "if we zoom in, out
+     * enable and in disable and vice versa, and once disabled it gets removed —
+     * that looks bad. Keep it disabled, do not remove the button." This
+     * supersedes the same-day "vanishes in place" call, and it covers EVERY disc
+     * in the column, the fit disc included. A control that blinks out of the
+     * column the moment it is spent teaches nothing about why; a dimmed one that
+     * stays where the thumb left it says "this is the end of that direction" and
+     * is still the target when the camera moves back. Slots are fixed either way
+     * (fit, ♿, +, − top→bottom on narrow — the `order` rules in pickerStyles),
+     * so nothing under the thumb moves at any camera now.
+     *
+     * `hidden` is therefore cleared on all three discs unconditionally: earlier
+     * builds could have left it set, and a stale one would strand a disc out of
+     * the column with nothing left to bring it back. The attribute still means
+     * something here — 3D empties the column, and wide never draws the fit disc —
+     * so the CSS rules for it stay.
      *
      * WHAT "+" READS, at the other end (owner, 2026-09-06, from the phone: "if
      * we already deep where we selecting the seat, plus not make further

package/dist/index.d.ts

@@ -3921,6 +3921,14 @@ declare class SeatPicker implements GaPromptPicker {
     private buildArenaChrome;
     /** Keep the camera's fitted viewport clear of measured multi-floor chrome. */
     /** @internal */ syncArenaViewportInsets(): void;
+    /**
+     * The phone zoom column is a SOFT bottom clearance instead (owner, 2026-09-07
+     * capture: the discs sat on the Cm/Cn blocks with a third of the map above
+     * the venue empty): a venue short enough to fit above the column is centred
+     * in that band, a taller one keeps the whole map. Duck-typed for an older
+     * @seatlayer/core without the hook.
+     */
+    /** @internal */ syncFitClearance(): void;
     /** Reflect the engine's current LOD rung onto the pill group. */
     /** @internal */ syncRung(): void;
     /**
@@ -3933,32 +3941,32 @@ declare class SeatPicker implements GaPromptPicker {
      * carries "+" and "−" and never shows the fit disc (CSS, see pickerStyles),
      * but "−" answers to the same reading there.
      *
-     * GONE, NOT DIMMED (owner call 2026-09-06, from real-iPhone captures, and
-     * the second time this had been asked for). The rationale before that was
-     * that a control which stays put and plainly cannot be pressed says "you are
-     * already looking at everything" without moving the target. It did not: two
-     * greyed discs at the arrival view were read as a broken map, and they are
-     * the FIRST thing a buyer sees, before they have any model of the ladder
-     * they are at the top of. So "−", the fit disc and "+" all left the column
-     * at their limits, and returned the moment there was a step to take.
-     *
-     * + AND − DO NOT LEAVE ANY MORE (owner call 2026-09-07, real-iPhone
-     * capture): "+ and − must always be in the same place." With three discs
-     * free to come and go, a corner-anchored column that grows upward reshuffled
-     * the two discs a buyer actually aims at — "sometimes + shows at the bottom
-     * and − at the very top and two in between". A control that never moves is
-     * worth more than a column with no dim in it, so this supersedes the
-     * 2026-09-06 call FOR "+" AND "−": they hold fixed adjacent slots (+ above
-     * −, see the `order` rules in pickerStyles) and go `disabled` at their
-     * limits, which the `.sl-zoom>button:disabled` rule dims. Both layouts —
-     * wide hid "−" at the venue fit too, which moved "+" there as well.
-     *
-     * THE FIT DISC STILL LEAVES, and it is the top disc on narrow now, so its
-     * departure moves nothing below it. `hidden`, and a CSS rule loud enough to
-     * beat the narrow `display:flex` on it. display:none, so the column closes
-     * the gap rather than leaving the ♿ floating a disc off the corner — which
-     * is also why the ♿ menu is re-bounded afterwards: its panel is clamped to
-     * the room above a button that may have just moved.
+     * THE HISTORY, BECAUSE IT WENT BOTH WAYS TWICE. Originally every disc dimmed
+     * at its limit. On 2026-09-06, from real-iPhone captures, they LEFT instead:
+     * two greyed discs at the arrival view were read as a broken map, and they
+     * are the FIRST thing a buyer sees, before they have any model of the ladder
+     * they are at the top of. Then on 2026-09-07 (morning) "+" and "−" came back
+     * as fixed slots that vanished in place, because a corner-anchored column
+     * that grows upward reshuffled the two discs a buyer actually aims at —
+     * "sometimes + shows at the bottom and − at the very top and two in between".
+     *
+     * A DISC AT ITS LIMIT DIMS IN PLACE AND NEVER LEAVES (owner call 2026-09-07,
+     * evening, off a phone capture of the buyer picker): "if we zoom in, out
+     * enable and in disable and vice versa, and once disabled it gets removed —
+     * that looks bad. Keep it disabled, do not remove the button." This
+     * supersedes the same-day "vanishes in place" call, and it covers EVERY disc
+     * in the column, the fit disc included. A control that blinks out of the
+     * column the moment it is spent teaches nothing about why; a dimmed one that
+     * stays where the thumb left it says "this is the end of that direction" and
+     * is still the target when the camera moves back. Slots are fixed either way
+     * (fit, ♿, +, − top→bottom on narrow — the `order` rules in pickerStyles),
+     * so nothing under the thumb moves at any camera now.
+     *
+     * `hidden` is therefore cleared on all three discs unconditionally: earlier
+     * builds could have left it set, and a stale one would strand a disc out of
+     * the column with nothing left to bring it back. The attribute still means
+     * something here — 3D empties the column, and wide never draws the fit disc —
+     * so the CSS rules for it stay.
      *
      * WHAT "+" READS, at the other end (owner, 2026-09-06, from the phone: "if
      * we already deep where we selecting the seat, plus not make further