@aurodesignsystem-dev/auro-formkit 0.0.0-pr1515.4 → 0.0.0-pr1518.0

package/components/datepicker/dist/auro-calendar-cell.d.ts

@@ -253,6 +253,12 @@ export class AuroCalendarCell extends LitElement {
      * Buttons stay tabindex="-1" because DOM focus stays on the grid wrapper —
      * arrow keys move the active cell imperatively and the live region carries
      * the SR announcement.
+     *
+     * Refuses to activate out-of-range cells: those are aria-hidden, have no
+     * click/focus handlers, and are filtered out of `getFocusableCells`. The
+     * active class showing on a disabled cell would be visually misleading,
+     * so this guard is the single source of truth across every code path
+     * that might call setActive (keyboard nav, focus restore, cell click).
      * @returns {void}
      */
     setActive(): void;

package/components/datepicker/dist/auro-calendar.d.ts

@@ -151,6 +151,14 @@ export class AuroCalendar extends RangeDatepicker {
      * @private
      */
     private activeCellDate;
+    /**
+     * Cached reference to the active cell host. Set by setActiveCell and
+     * refreshed by scrollToActiveCell when its cache check misses (stale
+     * or missing). Lets scrollToActiveCell skip a full cell scan on each
+     * arrow key.
+     * @private
+     */
+    private _activeCell;
     /**
      * Whether the #calendarGrid wrapper currently has focus.
      * Used to determine whether the visualFocus ring should be shown.
@@ -463,7 +471,28 @@ export class AuroCalendar extends RangeDatepicker {
      */
     private hoveredDateChanged;
     /**
-     * Scrolls the calendar to ensure the month containing the active cell is visible.
+     * Scrolls the calendar so the active cell is visible.
+     *
+     * Walks the flat tree (rendered, slot-aware) outward from the active
+     * cell's button and calls `scrollBy` on every vertically-scrollable
+     * ancestor by whatever delta still separates the cell from that
+     * ancestor's viewport. Native `scrollIntoView` is not used because the
+     * cell sits inside multiple nested scroll containers (the dropdown bib's
+     * `<dialog>`, the bibtemplate's `#bodyContainer`) and the algorithm only
+     * scrolls one of them on its own, leaving the cell short of the
+     * viewport in mobile fullscreen.
+     *
+     * Uses `behavior: 'auto'` (the spec's universally-supported non-animated
+     * value) so each `scrollBy` resolves synchronously and the next
+     * iteration's `getBoundingClientRect` reads post-scroll positions
+     * accurately. This also satisfies `prefers-reduced-motion` users — the
+     * scroll containers do not set CSS `scroll-behavior: smooth`, so `auto`
+     * is effectively instant.
+     *
+     * The active cell is looked up from the cache populated by
+     * `setActiveCell`. On a cache miss (stale or absent) the cache is
+     * refreshed from a single full scan so subsequent calls stay on the
+     * fast path.
      * @private
      * @returns {void}
      */