@optionfactory/fml 9.0.0-rc1 → 9.0.0-rc11

package/README.md

@@ -13,7 +13,7 @@ An http client
 ## ful
 A no-build web components library based on ftl
 
-ful fields report their values through `ful-form`'s intercepted submit: a plain `<form>` carrying them submits none of their values. Expressions compare strictly (`==` is `===`, and there is no coercing spelling), and message placeholders are `\w+` names: `{amount}` yes, `{user-name}` no.
+ful fields report their values through `ful-form`'s intercepted submit: a plain `<form>` carrying them submits none of their values. Expressions compare strictly (`==` is `===`, and there is no coercing spelling), and message placeholders are `\w+` names: `{amount}` yes, `{user-name}` no. Every field names its control in the markup, a `<label for>` pointing at it or `aria-labelledby` where the control is not something a `for` may target, so an accessibility audit and the browser's autofill read the label too and not assistive technology alone.
 
 ### Localization
 
@@ -73,7 +73,7 @@ ful.AsyncEvents.asyncOn(wizard, 'section:requested:dettagli', async (e) => {
 });
 ```
 
-The component awaits the union of the answers: the loading ring covers the wait, a failed delivery paints the section's problems and rejects the wizard's `move()`, and nobody listening is a plain activation at zero cost, so server-rendered sections never use the mechanism at all. `refresh()` re-fires explicitly (wizard by name or section, tabs by index or section; dialog and drawer argument-less), the drawer's `update()` keeping its own open-answer-deliver cycle.
+The component awaits the union of the answers: the loading ring covers the wait, a failed delivery paints the section's problems and rejects the wizard's `move()`, and nobody listening is a plain activation at zero cost, so server-rendered sections never use the mechanism at all. `refresh()` re-fires explicitly (wizard by name or section, tabs by index or section; dialog and drawer argument-less), the `update()` of the drawer and the dialog keeping its own open-answer-deliver cycle.
 
 The palette is `light-dark()` based and follows the page's `color-scheme` alone: pin `color-scheme: light` to disable the dark side, declare `light dark` to follow the os, `dark` to force it; the library declares nothing itself, and it works per-subtree too. The theme's ink pairs hold WCAG AA in both schemes, kept honest by a suite that computes the ratios; wherever the accent is read instead of filled (ghost outlines, done steps, success toasts) use `--ful-accent-ink`, the accent tuned for text.
 
@@ -83,10 +83,9 @@ See `examples/ful/kitchen-sink.html` for a page showing every component in its n
 
 fml targets evergreen browsers from spring 2024. The hard floor is Chrome/Edge 123 (March 2024), Firefox 125 (April 2024) and Safari 17.5 (May 2024), set by the newest platform features the library leans on everywhere: `light-dark()`, the Popover API, `Promise.withResolvers`, `:has()` and native CSS nesting. Below the floor, script or styling fail outright.
 
-Two features degrade instead of breaking under newer floors of their own, and another carries its own fallback:
+One feature degrades instead of breaking under a newer floor of its own, and another carries its own fallback:
 
 - the flash guard that keeps a field invisible until it has rendered is a custom state matched with `:state()`, Baseline since May 2024: Chrome/Edge 125, Firefox 126, Safari and iOS 17.4, so Safari is already below the hard floor and only Chrome 123-124 and Firefox 125 are affected. There the rule is dropped and a field shows for the moment between being parsed and being rendered
-- the fields' label and description wiring uses aria element reflection, Baseline since April 2025: an older browser keeps the visible layout intact while assistive technology silently loses the label and description associations
 - anchored popovers (the tooltip's note, the select's dropdown, the filter and boolean-value menus) need CSS anchor positioning: Chrome/Edge 129 (September 2024), Safari 26 (September 2025), Firefox 147 (January 2026; Firefox's support is partial against the full specification, but covers the subset fml uses, `anchor-name`, `position-anchor`, `position-area` (Baseline since January 2026), `anchor()` and `anchor-size()`). Below these a hand-placed fallback keeps the popovers anchored beside their invoker, and never runs where the css works
 
 On iOS every browser runs the system WebKit, so the floor reads in iOS versions: iOS 17.5 (May 2024) or newer, which every iPhone from the XS/XR (2018) onward can reach; the anchored popovers fall back to hand placing below iOS 26 (September 2025).

package/dist/custom-elements.json

@@ -11,14 +11,28 @@
           "name": "Tooltip",
           "tagName": "ful-tooltip",
           "customElement": true,
-          "description": "An info affordance: a themed icon button toggling a small popover with a short explanation, opened by click and by keyboard like a button, dismissed by Escape or an outside click. placement picks the side the note sits on: bottom (default), top, left or right.",
+          "description": "An info affordance: a themed icon button toggling a small popover with a short explanation, opened by click and by keyboard like a button, dismissed by Escape or an outside click. placement picks the side the note sits on: top (default), bottom, left or right.",
           "attributes": [
             {
               "name": "placement",
-              "description": "Which side of the trigger the note opens on: bottom (the default), top, start or end. The library places the note itself on every platform, so the side is the same everywhere.",
+              "description": "Which side of the trigger the note opens on: top (the default), bottom, left or right. Above by default because a note opening downwards covers the control the marker explains. The library places the note itself on every platform, so the side is the same everywhere.",
               "type": {
                 "text": "string"
               }
+            },
+            {
+              "name": "icon",
+              "description": "The ful-icon the marker shows, for a tooltip meaning something other than plain information. Defaults to the page's Tooltip.config.icon; a name the library does not paint is declared by the page as ful-icon[name='...'] { mask-image: ... }.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "describes",
+              "description": "For a tooltip standing in a field: the note joins the accessible description of that field's control, announced on reaching the field rather than only on opening the marker, and the marker leaves the tab order so a form of hinted fields costs no extra keystrokes to walk. The marker stays clickable, and keeps its tab stop wherever nothing took the note.",
+              "type": {
+                "text": "boolean"
+              }
             }
           ],
           "slots": [
@@ -34,7 +48,7 @@
           "name": "Dialog",
           "tagName": "ful-dialog",
           "customElement": true,
-          "description": "A modal dialog on the native platform: header, body and buttons, the header attribute naming its heading, opened by any element carrying dialog-target set to its id, or programmatically through open()/ask(), which resolve with the data-result of the button that closed the dialog (null on Escape). Longer explanations belong here, shorter ones in ful-tooltip.",
+          "description": "A modal dialog on the native platform: header, body and buttons, the header attribute naming its heading, opened by any element carrying dialog-target set to its id, or programmatically through open()/ask(), which answer with how the dialog ended, or through update(callback), which opens it on a loading state and then shows either what the callback delivered or the problems of a rejection. Longer explanations belong here, shorter ones in ful-tooltip.",
           "attributes": [
             {
               "name": "header",
@@ -42,22 +56,40 @@
               "type": {
                 "text": "string"
               }
+            },
+            {
+              "name": "requires-answer",
+              "description": "For the dialog that must be answered: the close button is not rendered and Escape is refused, so the only way out is a button carrying a result. Both, since a close button withheld while Escape still worked would be decoration rather than a rule.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "close-on-submit",
+              "description": "For the dialog whose answer is a form succeeding rather than a button being pressed: its own form submitting successfully closes it and answers with the response. Opt in, and its own form only, a ful-form the body holds directly, since a ful-table wraps its filters in a form of its own and searching one is not the dialog being answered. Such a dialog renders no acknowledge button of its own, the form's submit being its answer.",
+              "type": {
+                "text": "boolean"
+              }
             }
           ],
           "slots": [
+            {
+              "name": "header",
+              "description": "Content beside the title and before it: an icon, a badge, a status. It sits outside the heading rather than in it, the header attribute setting the heading through text."
+            },
             {
               "name": "",
               "description": "The dialog body."
             },
             {
               "name": "buttons",
-              "description": "Buttons closing the dialog; each carries a data-result that ask() resolves with. Without this slot a localized acknowledge button is shown."
+              "description": "Buttons closing the dialog; each carries a data-result that the answer carries back. Without this slot a localized acknowledge button is shown. A dialog closing on its form renders none either way, so the slot is for buttons beside the form, not for suppressing one."
             }
           ],
           "events": [
             {
               "name": "close",
-              "description": "Fired when the dialog closes, carrying the data-result of the button that closed it, or null on Escape; ask() and open() resolve with the same answer, and a dialog leaving the document while open answers its waiters with null.",
+              "description": "Fired when the dialog closes, carrying how it ended: dismissed tells a cancel from an answer, result the data-result of the button that closed it, response what a submit answered with. ask() and open() resolve with the same object, and a dialog leaving the document while open answers its waiters with a dismissal.",
               "type": {
                 "text": "CustomEvent"
               }
@@ -91,9 +123,20 @@
               "type": {
                 "text": "string"
               }
+            },
+            {
+              "name": "close-on-submit",
+              "description": "For the drawer whose ending is a form succeeding rather than its close button being pressed: the form its content holds directly submitting successfully closes it, the close event carrying the response. Opt in, and its own form only, since a ful-table wraps its filters in a form of its own and searching one is not the drawer finishing.",
+              "type": {
+                "text": "boolean"
+              }
             }
           ],
           "slots": [
+            {
+              "name": "header",
+              "description": "Content beside the title and before it: an icon, a badge, a status. It sits outside the heading rather than in it, update() setting the title through textContent and taking anything nested there with it."
+            },
             {
               "name": "",
               "description": "The drawer body, shown when update() never replaced it."
@@ -102,7 +145,7 @@
           "events": [
             {
               "name": "close",
-              "description": "Fired when the drawer closes, by its close button or Escape.",
+              "description": "Fired when the drawer closes, carrying how it ended: dismissed tells the close button and Escape from a form that closed it under close-on-submit, and response what that submit answered with, a save answering with no body at all being a save all the same.",
               "type": {
                 "text": "CustomEvent"
               }
@@ -296,6 +339,13 @@
               "type": {
                 "text": "boolean"
               }
+            },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token every field in the form takes unless it declares one of its own, copied onto the form element the host renders. A form cannot pass it down the way the platform would: each control carries form=\"\" so that the host is the only thing that submits, which leaves it with no form owner to inherit through, so the fields read it off the form instead.",
+              "type": {
+                "text": "string"
+              }
             }
           ],
           "slots": [],
@@ -398,11 +448,11 @@
           "name": "Input",
           "tagName": "ful-input",
           "customElement": true,
-          "description": "A labelled text input. Use type to pick any native input type, or textarea; keep names the characters that survive a keystroke and reject the ones that do not, the caret staying among the survivors, and the uppercase and trim claims shape the value before it is read; v-type=number decodes the value to a number, blank staying null and a value that does not decode kept as it is, an undeclared type defaulting to number. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
+          "description": "A labelled text input. Use type to pick any native input type, the keypad types numeric and decimal, or textarea; keep names the characters that survive a keystroke and reject the ones that do not, the caret staying among the survivors, and the uppercase and trim claims shape the value before it is read; v-type=number decodes the value to a number, blank staying null and a value that does not decode kept as it is, an undeclared type defaulting to number. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -442,6 +492,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -515,7 +572,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -555,6 +612,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -731,7 +795,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -771,6 +835,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -865,7 +936,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -905,6 +976,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -999,7 +1077,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -1039,6 +1117,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -1236,12 +1321,31 @@
               "name": "caption",
               "description": "The caption of the table."
             },
+            {
+              "name": "empty",
+              "description": "Shown in place of the rows when a load returns none, replacing the localized default message."
+            },
             {
               "name": "footer",
               "description": "Content rendered in the table footer."
             }
           ],
-          "events": []
+          "events": [
+            {
+              "name": "load:success",
+              "description": "Fired once a load has settled, after the rows are in place and the busy state is gone, carrying the page response and the three requests that asked for it. Not fired for a load a newer one superseded, which owns nothing.",
+              "type": {
+                "text": "CustomEvent"
+              }
+            },
+            {
+              "name": "load:failure",
+              "description": "Fired when a load rejects, after the error row is shown, carrying the exception and the three requests. Telling this from an empty result is what the aria-busy attribute alone cannot do.",
+              "type": {
+                "text": "CustomEvent"
+              }
+            }
+          ]
         },
         {
           "kind": "class",
@@ -1325,7 +1429,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -1365,6 +1469,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -1445,7 +1556,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -1485,6 +1596,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -1565,7 +1683,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -1605,6 +1723,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -1752,11 +1877,11 @@
           "name": "TextFilter",
           "tagName": "ful-filter-text",
           "customElement": true,
-          "description": "A ful-table filter over text, with an operator such as CONTAINS or STARTS_WITH and a case sensitivity. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only. A multiple ful-select used as a filter emits the bare value array the in-list annotations expect.",
+          "description": "A ful-table filter over text, with an operator such as CONTAINS or STARTS_WITH and a case sensitivity. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "type": {
                 "text": "string"
               }
@@ -1796,6 +1921,13 @@
                 "text": "boolean"
               }
             },
+            {
+              "name": "autocomplete",
+              "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
+              "type": {
+                "text": "string"
+              }
+            },
             {
               "name": "disabled",
               "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
@@ -1874,6 +2006,179 @@
             }
           ]
         },
+        {
+          "kind": "class",
+          "name": "InFilter",
+          "tagName": "ful-filter-in",
+          "customElement": true,
+          "description": "A ful-table filter over set membership, answering for both of data-jpa's set annotations: InEnum and InList take the same array of values and no operator, differing only in what the server converts them to. The vocabulary comes from wherever a select's does, slotted options or a loader, and the selection is always multiple, an empty one contributing nothing rather than an empty array.",
+          "attributes": [
+            {
+              "name": "name",
+              "description": "The field name the surrounding form submits the selection under.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "loader",
+              "description": "The registered component name the select loads its vocabulary through; loaders:select when absent.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "k-type",
+              "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or bool.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "src",
+              "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "method",
+              "description": "The method the vocabulary is fetched with; POST when absent.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "mode",
+              "description": "chunked asks the endpoint per query instead of fetching the vocabulary once, for a list too large to hold.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "preload",
+              "description": "Fetches the vocabulary while the element upgrades rather than on first use. The field paints immediately either way; the options arrive when they arrive.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "revision",
+              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it. Left valueless, the revision the registry's 'revision' component answers is used, so a page states its build once instead of every element repeating it.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "k-expr",
+              "description": "The expression yielding an option's key, evaluated against each row of the response. Set it together with l-expr to shape a response without a mapper component.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "l-expr",
+              "description": "The expression yielding an option's label, evaluated against each row of the response.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "d-expr",
+              "description": "The expression yielding the rows from the response body; the body itself when absent.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "m-expr",
+              "description": "The expression yielding an option's metadata, evaluated against each row; the whole row when absent.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "response-mapper",
+              "description": "The registered component name that turns a response into { key, label, metadata } entries. The k-expr/l-expr pair takes precedence; without either, the response is read as positional rows.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "disabled",
+              "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "readonly",
+              "description": "Renders the control but does not let it be edited. A readonly field still contributes its value to the form.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "required",
+              "description": "Marks the field as required for assistive technologies and shows the required marker on its label.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "value",
+              "description": "Comma separated list of the selected keys. Empty contributes nothing, so the table drops the filter rather than sending an empty set.",
+              "type": {
+                "text": "string"
+              }
+            },
+            {
+              "name": "multiple",
+              "description": "Always on for this element: a set of one is still a set, and a single selection would answer a bare key where the filter request wants an array.",
+              "type": {
+                "text": "boolean"
+              }
+            },
+            {
+              "name": "item-list",
+              "description": "Shows the selection as a ful-item-list under the control as well, in addition to the field itself (the label for a single select, the ful-badge chips when multiple).",
+              "type": {
+                "text": "boolean"
+              }
+            }
+          ],
+          "slots": [
+            {
+              "name": "",
+              "description": "The label of the field."
+            },
+            {
+              "name": "info",
+              "description": "Extra content rendered next to the label, for a hint or a help icon."
+            },
+            {
+              "name": "before",
+              "description": "An addon rendered inside the input group, before the control."
+            },
+            {
+              "name": "after",
+              "description": "An addon rendered inside the input group, after the control."
+            },
+            {
+              "name": "dropdown",
+              "description": "Replaces the template used to render the options."
+            }
+          ],
+          "events": [
+            {
+              "name": "change",
+              "description": "Fired with the selected keys, or undefined when nothing is picked.",
+              "type": {
+                "text": "CustomEvent"
+              }
+            }
+          ]
+        },
         {
           "kind": "class",
           "name": "Select",
@@ -1932,7 +2237,7 @@
             },
             {
               "name": "revision",
-              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it.",
+              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it. Left valueless, the revision the registry's 'revision' component answers is used, so a page states its build once instead of every element repeating it.",
               "type": {
                 "text": "string"
               }
@@ -2282,6 +2587,14 @@
             "module": "dist/fml.mjs"
           }
         },
+        {
+          "kind": "custom-element-definition",
+          "name": "ful-filter-in",
+          "declaration": {
+            "name": "InFilter",
+            "module": "dist/fml.mjs"
+          }
+        },
         {
           "kind": "custom-element-definition",
           "name": "ful-select",