forty-cdk 0.14.0 → 0.15.0

package/README.md

@@ -36,7 +36,7 @@ Optional — install only if you use the matching entry point / primitives:
 
 ## Primitives
 
-Every primitive ships as its own **secondary entry point** — import `ForDialog` from `forty-cdk/dialog`, `ForAccordion` from `forty-cdk/accordion`, and so on — backed by the shared `forty-cdk/core` entry point. Each lives in its own folder under `projects/forty-cdk/` with its own `README.md` documenting its anatomy, API, keyboard interaction and styling hooks. The `@internationalized/date` adapters live in a dedicated `forty-cdk/internationalized-date` entry point so that optional peer stays truly optional. The main `forty-cdk` barrel is **intentionally empty** (it exports no symbols): always import from the specific `forty-cdk/<primitive>` entry point. Standalone directives plus `"sideEffects": false` mean your bundle only ever includes the primitives you import.
+Every primitive ships as its own **secondary entry point** — import `ForDialog` from `forty-cdk/dialog`, `ForAccordion` from `forty-cdk/accordion`, and so on — backed by the shared `forty-cdk/core` entry point. Each lives in its own folder under `projects/forty-cdk/` with its own `README.md` documenting its anatomy, API, keyboard interaction and styling hooks. The `@internationalized/date` adapters live in a dedicated `forty-cdk/internationalized-date` entry point so that optional peer stays truly optional. The cross-primitive contract types a primitive's public API references — `WritingDirection`, `VetoableEvent`, `DateAdapter`, `FloatingSide`, … — are published by [`forty-cdk/shared`](shared); the main `forty-cdk` barrel is **intentionally empty** (it exports no symbols), so always import primitives from the specific `forty-cdk/<primitive>` entry point. Standalone directives plus `"sideEffects": false` mean your bundle only ever includes the primitives you import.
 
 The tables below group the primitives by purpose. The link on each name opens that primitive's README — the canonical reference for which HTML element each directive belongs on, its inputs / outputs, `data-*` attributes and keyboard map.
 

package/carousel/README.md

@@ -110,6 +110,11 @@ the defaults with `startLabel` / `stopLabel` inputs:
 <button forCarouselRotationControl startLabel="Play slideshow" stopLabel="Pause slideshow"></button>
 ```
 
+Both defaults come from the scope's `rotationStartLabel` / `rotationStopLabel`
+(see [Localizing the default labels](#localizing-the-default-labels)); set either
+input to `null` when the button carries a visible text label and you don't want
+an `aria-label` overriding it.
+
 **Programmatic control** via `exportAs`:
 
 ```html
@@ -189,16 +194,19 @@ captured, so page scrolling on the perpendicular axis is unaffected.
 
 ## Localizing the default labels
 
-Each slide's default `aria-label` is the positional `"N of M"` string, and each
-indicator's is `"Go to slide N"`. Localize both centrally with
-`provideForCarouselDefaults` instead of setting `ariaLabel` on every slide and
-indicator:
+Each slide's default `aria-label` is the positional `"N of M"` string, each
+indicator's is `"Go to slide N"`, and the rotation control's swaps between
+`"Start automatic slide show"` and `"Stop automatic slide show"`. Localize them
+all centrally with `provideForCarouselDefaults` instead of setting `ariaLabel` on
+every slide and indicator:
 
 ```ts
 providers: [
   provideForCarouselDefaults({
     slideLabel: (position, total) => `Diapositiva ${position} de ${total}`,
     indicatorLabel: (position) => `Ir a la diapositiva ${position}`,
+    rotationStartLabel: 'Iniciar la presentación',
+    rotationStopLabel: 'Detener la presentación',
   }),
 ];
 ```
@@ -206,7 +214,8 @@ providers: [
 `position` is the 1-based slide index and `total` is the slide count. Overrides
 merge with the parent scope, so you can localize just the labels and inherit the
 rest of the defaults. A per-element `ariaLabel` on `[forCarouselSlide]` /
-`[forCarouselIndicator]` still takes precedence over the localized default.
+`[forCarouselIndicator]` still takes precedence over the localized default, as do
+`[startLabel]` / `[stopLabel]` on `[forCarouselRotationControl]`.
 
 ## API
 
@@ -229,8 +238,8 @@ All inputs are on `[forCarousel]` unless noted.
 | `ariaLabel` (on `[forCarouselIndicators]`)       | `string \| null`               | Label for the picker group.<br>**Default:** `null`                                                                                                         |
 | `ariaLabel` (on `[forCarouselSlide]`)            | `string \| null`               | Override the positional "N of M" label.<br>**Default:** `null`                                                                                             |
 | `disabled` (on `[forCarouselIndicator]`)         | `boolean`                      | Disable this indicator.<br>**Default:** `false`                                                                                                            |
-| `startLabel` (on `[forCarouselRotationControl]`) | `string`                       | Accessible name while rotation is stopped.<br>**Default:** `'Start automatic slide show'`                                                                  |
-| `stopLabel` (on `[forCarouselRotationControl]`)  | `string`                       | Accessible name while rotation is playing.<br>**Default:** `'Stop automatic slide show'`                                                                   |
+| `startLabel` (on `[forCarouselRotationControl]`) | `string \| null`               | Accessible name while rotation is stopped.<br>**Default:** scope `rotationStartLabel` (`'Start automatic slide show'`)                                     |
+| `stopLabel` (on `[forCarouselRotationControl]`)  | `string \| null`               | Accessible name while rotation is playing.<br>**Default:** scope `rotationStopLabel` (`'Stop automatic slide show'`)                                       |
 
 Reflected on the `[forCarousel]` host:
 
@@ -298,8 +307,10 @@ Implements the [WAI-ARIA Carousel pattern](https://www.w3.org/WAI/ARIA/apg/patte
   accessibility tree and focus order.
 - The indicator group should be labelled (e.g. `ariaLabel="Choose slide to display"`).
 - The current indicator is marked with `aria-current="true"`.
-- Prev/next buttons use native `disabled` so they are removed from the tab order when
-  at the boundary without loop.
+- Prev/next buttons never use the native `disabled` attribute. At a boundary without `loop`
+  they reflect `aria-disabled="true"` + `data-disabled` and ignore activation, so a keyboard
+  user who reaches the last slide keeps focus on the button instead of being dropped to
+  `<body>`. Style the boundary state off `[data-disabled]`, never `:disabled`.
 - The viewport carries `aria-live` and `aria-atomic="false"`. While the carousel is actively
   auto-rotating, `aria-live` is `"off"` so advancing slides do not bombard the screen reader.
   When stopped or paused, it is `"polite"` so manual navigation announces. The per-slide
@@ -365,6 +376,13 @@ children, unless noted otherwise:
 | `data-rotating` | On `[forCarousel]` — actively rotating right now        |
 | `data-autoplay` | On `[forCarousel]` — the `autoplay` input is `true`     |
 
+### Boundary styling hooks
+
+| Attribute       | When present                                              |
+| --------------- | --------------------------------------------------------- |
+| `data-disabled` | On `[forCarouselPrevious]` — at index 0 without `loop`    |
+| `data-disabled` | On `[forCarouselNext]` — at the last index without `loop` |
+
 ### Drag styling hooks
 
 | Attribute       | Host                    | When present                           |

package/date-field/README.md

@@ -118,17 +118,17 @@ export class DobFormField {
 
 ### `ForDateField`
 
-| Property      | Type                                                  | Description                                                                                                                                |
-| ------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| `value`       | `model<D \| null>`                                    | Two-way bindable entered date, or `null` while any segment is empty. The `FormValueControl` backing.<br>**Default:** `null`                |
-| `minDate`     | `input<D \| null>`                                    | Minimum date (inclusive). A composed value below it is clamped up. Named `minDate` — see note below.<br>**Default:** `null`                |
-| `maxDate`     | `input<D \| null>`                                    | Maximum date (inclusive). A composed value above it is clamped down.<br>**Default:** `null`                                                |
-| `granularity` | `input<'day' \| 'hour' \| 'minute' \| 'second'>`      | Date-time precision. `'day'` is date-only; coarser-than-day appends time segments. See below.<br>**Default:** `'day'`                      |
-| `hourCycle`   | `input<12 \| 24 \| null>`                             | 12/24-hour cycle for the time segments. `null` → locale. 12-hour adds the AM/PM segment.<br>**Default:** `null`                            |
-| `locale`      | `input<string \| null>`                               | BCP 47 locale driving segment order, separators, and month name. `null` → runtime locale.<br>**Default:** `null`                           |
-| `placeholder` | `input<Partial<Record<DateTimeSegmentType, string>>>` | Per-segment placeholder while empty. Unspecified parts fall back to `dd` / `mm` / `yyyy` / `hh` / `mm` / `ss` / `--`.<br>**Default:** `{}` |
-| `ariaLabel`   | `input<string \| null>`                               | Accessible name for the group. Emits no `aria-label` while `null`.<br>**Default:** `null`                                                  |
-| `dir`         | `input<'ltr' \| 'rtl' \| null>`                       | Writing direction. `null` resolves the ambient direction; mirrors ArrowLeft / ArrowRight segment navigation.<br>**Default:** `null`        |
+| Property      | Type                                             | Description                                                                                                                                |
+| ------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `value`       | `model<D \| null>`                               | Two-way bindable entered date, or `null` while any segment is empty. The `FormValueControl` backing.<br>**Default:** `null`                |
+| `minDate`     | `input<D \| null>`                               | Minimum date (inclusive). A composed value below it is clamped up. Named `minDate` — see note below.<br>**Default:** `null`                |
+| `maxDate`     | `input<D \| null>`                               | Maximum date (inclusive). A composed value above it is clamped down.<br>**Default:** `null`                                                |
+| `granularity` | `input<'day' \| 'hour' \| 'minute' \| 'second'>` | Date-time precision. `'day'` is date-only; coarser-than-day appends time segments. See below.<br>**Default:** `'day'`                      |
+| `hourCycle`   | `input<12 \| 24 \| null>`                        | 12/24-hour cycle for the time segments. `null` → locale. 12-hour adds the AM/PM segment.<br>**Default:** `null`                            |
+| `locale`      | `input<string \| null>`                          | BCP 47 locale driving segment order, separators, and month name. `null` → runtime locale.<br>**Default:** `null`                           |
+| `placeholder` | `input<Partial<Record<SegmentType, string>>>`    | Per-segment placeholder while empty. Unspecified parts fall back to `dd` / `mm` / `yyyy` / `hh` / `mm` / `ss` / `--`.<br>**Default:** `{}` |
+| `ariaLabel`   | `input<string \| null>`                          | Accessible name for the group. Emits no `aria-label` while `null`.<br>**Default:** `null`                                                  |
+| `dir`         | `input<'ltr' \| 'rtl' \| null>`                  | Writing direction. `null` resolves the ambient direction; mirrors ArrowLeft / ArrowRight segment navigation.<br>**Default:** `null`        |
 
 Plus the shared `FormUiControl` members from `@angular/forms/signals`: `disabled`, `readonly`, `required`, `invalid`, `name`, `errors`, `touched` (bound automatically by `[formField]`).
 

package/date-range-field/README.md

@@ -158,17 +158,17 @@ export class StayFormField {
 
 ### `ForDateRangeField`
 
-| Property      | Type                                                  | Description                                                                                                                                       |
-| ------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `value`       | `model<DateRange<D> \| null>`                         | Two-way bindable committed range, or `null` while incomplete or out of order. The `FormValueControl` backing.<br>**Default:** `null`              |
-| `minDate`     | `input<D \| null>`                                    | Minimum date (inclusive) for both endpoints. A composed endpoint below it is clamped up. Named `minDate` — see note below.<br>**Default:** `null` |
-| `maxDate`     | `input<D \| null>`                                    | Maximum date (inclusive) for both endpoints. A composed endpoint above it is clamped down.<br>**Default:** `null`                                 |
-| `granularity` | `input<'day' \| 'hour' \| 'minute' \| 'second'>`      | Date-time precision shared by both endpoints. `'day'` is date-only; coarser-than-day appends time segments.<br>**Default:** `'day'`               |
-| `hourCycle`   | `input<12 \| 24 \| null>`                             | 12/24-hour cycle for the time segments. `null` → locale. 12-hour adds the AM/PM segment.<br>**Default:** `null`                                   |
-| `locale`      | `input<string \| null>`                               | BCP 47 locale driving segment order, separators, and month name. `null` → runtime locale.<br>**Default:** `null`                                  |
-| `placeholder` | `input<Partial<Record<DateTimeSegmentType, string>>>` | Per-segment placeholder while empty, applied to both endpoints.<br>**Default:** `{}`                                                              |
-| `ariaLabel`   | `input<string \| null>`                               | Accessible name for the whole range field group. Emits no `aria-label` while `null`.<br>**Default:** `null`                                       |
-| `dir`         | `input<'ltr' \| 'rtl' \| null>`                       | Writing direction. `null` resolves the ambient direction; mirrors ArrowLeft / ArrowRight segment navigation.<br>**Default:** `null`               |
+| Property      | Type                                             | Description                                                                                                                                       |
+| ------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `value`       | `model<DateRange<D> \| null>`                    | Two-way bindable committed range, or `null` while incomplete or out of order. The `FormValueControl` backing.<br>**Default:** `null`              |
+| `minDate`     | `input<D \| null>`                               | Minimum date (inclusive) for both endpoints. A composed endpoint below it is clamped up. Named `minDate` — see note below.<br>**Default:** `null` |
+| `maxDate`     | `input<D \| null>`                               | Maximum date (inclusive) for both endpoints. A composed endpoint above it is clamped down.<br>**Default:** `null`                                 |
+| `granularity` | `input<'day' \| 'hour' \| 'minute' \| 'second'>` | Date-time precision shared by both endpoints. `'day'` is date-only; coarser-than-day appends time segments.<br>**Default:** `'day'`               |
+| `hourCycle`   | `input<12 \| 24 \| null>`                        | 12/24-hour cycle for the time segments. `null` → locale. 12-hour adds the AM/PM segment.<br>**Default:** `null`                                   |
+| `locale`      | `input<string \| null>`                          | BCP 47 locale driving segment order, separators, and month name. `null` → runtime locale.<br>**Default:** `null`                                  |
+| `placeholder` | `input<Partial<Record<SegmentType, string>>>`    | Per-segment placeholder while empty, applied to both endpoints.<br>**Default:** `{}`                                                              |
+| `ariaLabel`   | `input<string \| null>`                          | Accessible name for the whole range field group. Emits no `aria-label` while `null`.<br>**Default:** `null`                                       |
+| `dir`         | `input<'ltr' \| 'rtl' \| null>`                  | Writing direction. `null` resolves the ambient direction; mirrors ArrowLeft / ArrowRight segment navigation.<br>**Default:** `null`               |
 
 The endpoint groups (`[forDateRangeFieldStart]` / `[forDateRangeFieldEnd]`) each accept an `ariaLabel` input for their own group label, falling back to the scope defaults (`'Start date'` / `'End date'`).
 

package/drag-drop/README.md

@@ -7,15 +7,15 @@ whole dialog around by its header — see [`[forFreeDrag]`](#free-drag).
 
 ## Keyboard
 
-| State  | Key         | Action                                            |
-| ------ | ----------- | ------------------------------------------------- |
-| Idle   | Arrow keys  | Move roving focus between items                   |
-| Idle   | Home / End  | Jump to first / last item                         |
-| Idle   | Space/Enter | **Lift** the focused item                         |
-| Lifted | Arrow keys  | Step the logical drop position                    |
-| Lifted | Home / End  | Jump the lifted item to the first / last position |
-| Lifted | Space/Enter | **Drop** (commits and emits `(dragDrop)`)         |
-| Lifted | Escape      | **Cancel** (no event, focus stays on item)        |
+| State  | Key         | Action                                                         |
+| ------ | ----------- | -------------------------------------------------------------- |
+| Idle   | Arrow keys  | Move roving focus between items                                |
+| Idle   | Home / End  | Jump to first / last item                                      |
+| Idle   | Space/Enter | **Lift** the focused item                                      |
+| Lifted | Arrow keys  | Step the logical drop position                                 |
+| Lifted | Home / End  | Jump the lifted item to the first / last position              |
+| Lifted | Space/Enter | **Drop** (commits, emits `(dragDrop)`, focus follows the item) |
+| Lifted | Escape      | **Cancel** (no event, focus stays on item)                     |
 
 Arrow direction follows the list's `orientation` and respects RTL via `dir`. In
 `orientation="mixed"` every arrow key steps the lifted item linearly in DOM order.
@@ -24,6 +24,21 @@ Arrow direction follows the list's `orientation` and respects RTL via `dir`. In
 
 Keyboard lifting, stepping, dropping, and cancellation are announced via ARIA live regions. Override the default messages at any injector scope via `provideForDragDropDefaults` (see Announcement customisation below). Free-drag is pointer-only — there is no WAI-ARIA pattern for "reposition an element", so `[forFreeDrag]` owns no role or ARIA state; the consumer is responsible for keeping the moved element fully usable at its default position.
 
+### Focus after a keyboard drop
+
+Applying the move in `(dragDrop)` destroys or re-inserts the lifted element, which would otherwise
+leave focus on `<body>`. So after a **keyboard** drop whose lifted item held focus, `[forDropList]`
+restores focus to the item at `currentIndex` in the target container on the next render — the same
+element the user just placed, whether it stayed in this list or transferred to a connected one.
+
+Two escape hatches:
+
+- **Focus something yourself** inside the `(dragDrop)` handler (a status region, a toolbar, the next
+  row). The restore only fires when focus has already fallen to `<body>`, so whatever you focus wins.
+- **Pointer drops are untouched** — focus is never moved after a mouse / touch / pen drop.
+
+If your handler leaves the data unchanged, nothing is detached and focus simply stays on the item.
+
 ## Pointer dragging
 
 When a pointer drag starts, the dragged item stays in place and reflects
@@ -119,7 +134,8 @@ stays in the dragged item's source slot.
 ```
 
 `[liveSort]` has no visible effect without a `[forDragPlaceholder]` template, and has no effect
-on keyboard dragging.
+on keyboard dragging. The drop index is resolved from the geometry measured at lift, so
+`[liveSort]` never changes which index a pointer path commits — it only moves the placeholder.
 
 ### Boundary & axis lock
 
@@ -198,6 +214,10 @@ preview is destroyed promptly.
   happens to render as a single row or single column resolves identically to `"horizontal"` /
   `"vertical"`.
 
+In a cross-list transfer each container resolves the drop index on **its own** `orientation` and
+`dir`, so a vertical list can be connected to a horizontal one (or to one in the opposite writing
+direction) and the pointer index lands on the target's axis.
+
 ```html
 <ul class="grid" forDropList orientation="mixed" (dragDrop)="onDrop($event)">
   @for (item of items(); track item.id) {
@@ -413,3 +433,7 @@ providers: [
   }),
 ];
 ```
+
+`total` is the number of valid drop positions in the list being announced: the item count for a
+same-list reorder, and one more than the item count for a transfer into a connected list (the
+append gap counts).

package/fesm2022/forty-cdk-calendar.mjs

@@ -1,7 +1,6 @@
 import * as i0 from '@angular/core';
 import { computed, InjectionToken, inject, signal, Injector, model, input, booleanAttribute, numberAttribute, linkedSignal, effect, afterNextRender, Directive, ElementRef, Injectable } from '@angular/core';
 import { compareDateOf, clampToBounds, Collection, createDefaults, IdGenerator, LiveAnnouncer, injectDateAdapter, injectTextDirection, adoptHostId, hostLabelledBy, registerHandle, hostAriaLabel, createFormatterCache, FOR_DATE_ADAPTER } from 'forty-cdk/core';
-export { FOR_DATE_ADAPTER, assertTimeCapable, injectDateAdapter } from 'forty-cdk/core';
 
 /**
  * Owns every `[min, max]` bounds question a `ForCalendar` asks: whole-month /