@optionfactory/fml 9.0.0-rc2 → 9.0.0-rc20

package/dist/vscode.html-custom-data.json

@@ -3,41 +3,71 @@
   "tags": [
     {
       "name": "ful-tooltip",
-      "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. (string)"
+          "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. (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: ... }. (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. (boolean)"
         }
       ]
     },
     {
       "name": "ful-dialog",
-      "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. Dialog.ask(header, body, buttons) and Dialog.confirm(header, body, labels) ask a question in a transient one, building, showing, answering and removing the element themselves; a confirm's cancel, close and Escape all answer the negative.",
       "attributes": [
         {
           "name": "header",
           "description": "The dialog's title, shown in its header. Text only; slot content into the body instead for anything richer. (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. (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. (boolean)"
         }
       ]
     },
     {
       "name": "ful-drawer",
-      "description": "A side panel drawer on the native dialog platform: a header with its title (the title attribute, or update()'s own) and close button, and a body that opens in a loading state, then shows either the content delivered by update(title, callback) (or the slotted one, when it is never updated) or the error a rejecting callback carries. placement picks the side, end by default, start its mirror. Any element carrying dialog-target set to its id opens it too.",
+      "description": "A side panel drawer on the native dialog platform: a header with its title (the header attribute, or update()'s own) and close button, and a body that opens in a loading state, then shows either the content delivered by update(header, callback) (or the slotted one, when it is never updated) or the error a rejecting callback carries. placement picks the side, end by default, start its mirror. Any element carrying dialog-target set to its id opens it too.",
       "attributes": [
         {
-          "name": "title",
+          "name": "header",
           "description": "The drawer's title, shown in its header. Text only, and also what update() re-titles the panel with. (string)"
         },
         {
           "name": "placement",
           "description": "Which edge the panel slides in from: end (the default) or start, following the page's writing direction. (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. (boolean)"
+        }
+      ]
+    },
+    {
+      "name": "ful-menu",
+      "description": "A menu of commands on the native popover platform: the invoker named by for toggles it, light dismiss and Escape come from the browser, and the element adds the menu semantics and the keyboard protocol (roving focus with the arrows, Home and End, type-ahead, Enter and Space to activate, Escape and every close handing the focus back to the invoker). The items are the buttons and links written inside it, kept as they are and given their menuitem role; activation is the item's own click, which the menu only follows by closing.",
+      "attributes": [
+        {
+          "name": "for",
+          "description": "The id of the invoker the menu belongs to: it toggles the menu, carries aria-haspopup and aria-expanded, and takes the focus back when the menu closes. Read once at the upgrade, so the invoker must already be in the page by then. (string)"
         }
       ]
     },
     {
       "name": "ful-toasts",
-      "description": "A transient feedback region, one per page: each show() (or a show-toast document event carrying the same detail) appends a toast that dismisses itself after its timeout, the element's timeout attribute or five seconds by default, and carries its own dismiss button. severity picks the theme and the announcement, info by default, success, warning and error, the error one announced as an alert; a Failure message shows its problems' reasons.",
+      "description": "A transient feedback region, one per page: each show() (or a show-toast document event carrying the same detail) appends a toast that dismisses itself after its timeout, the element's timeout attribute or five seconds by default, and carries its own dismiss button. severity picks the theme and the announcement, info by default, success, warning and error, the error one announced as an alert; a Failure message shows its problems' reasons. The timer holds while the toast is hovered or holds the focus, and action: { label, onClick } renders a button beside the message whose click answers and retires the toast, the same option travelling in the event detail.",
       "attributes": [
         {
           "name": "timeout",
@@ -51,7 +81,7 @@
       "attributes": [
         {
           "name": "active",
-          "description": "The index of the visible panel, zero based, reflected as the active attribute. Clicks, the arrow keys and the property all move it, each move answering with a change event. (number)"
+          "description": "The index of the visible panel, zero based, reflected as the active attribute. Clicks, the arrow keys and the property all move it, each move answering with a tabs:change event. (number)"
         }
       ]
     },
@@ -67,7 +97,7 @@
     },
     {
       "name": "ful-wizard",
-      "description": "A wizard: a progress of steps over one-of-N sections. The steps are declared as step elements in the steps slot, the sections as the slotless children, paired in order; each section may carry a data-step name, which is what move() answers to, next() and prev() walk the neighbors, and the current step is the aria-current=step claim carried in lockstep by the step and its section, so the chrome, including which section is shown, follows the claim alone. Each move answers with a change event.",
+      "description": "A wizard: a progress of steps over one-of-N sections. The steps are declared as step elements in the steps slot, the sections as the slotless children, paired in order; each section may carry a data-step name, which is what move() answers to, next() and prev() walk the neighbors, and the current step is the aria-current=step claim carried in lockstep by the step and its section, so the chrome, including which section is shown, follows the claim alone. Each move answers with a wizard:change event.",
       "attributes": [
         {
           "name": "progress",
@@ -110,6 +140,14 @@
         {
           "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. (string)"
+        },
+        {
+          "name": "track-changes",
+          "description": "Keeps track of the edits not saved yet: dirty answers whether a field the user edited since the last commit holds another value, the host matches :state(dirty) and the submit buttons carry a dot while it does. A successful submit commits, and so does the form once its fields have rendered; commit() is for a save of the page's own. (boolean)"
+        },
+        {
+          "name": "guard-leave",
+          "description": "Asks before the page is left while the form holds edits not saved yet, through the browser's own prompt. Implies track-changes. (boolean)"
         }
       ]
     },
@@ -141,11 +179,11 @@
     },
     {
       "name": "ful-input",
-      "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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -167,6 +205,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
@@ -199,7 +241,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -221,6 +263,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
@@ -309,7 +355,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -331,6 +377,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
@@ -375,7 +425,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -397,6 +447,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
@@ -441,7 +495,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -463,6 +517,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
@@ -546,6 +604,14 @@
         {
           "name": "page-size",
           "description": "How many rows a page asks the loader for, 10 by default. Stays live: writing it reloads from the first page, a table that has not been asked to load yet only recording it. (number)"
+        },
+        {
+          "name": "src",
+          "description": "The url the default loader asks for rows; without it the table loads from an in-memory loader fed through withLoader. Stays live: writing it builds the loader again and reloads from the first page, keeping the sort and the filters. (string)"
+        },
+        {
+          "name": "method",
+          "description": "The http method the default loader sends, GET by default. Stays live, as src does. (string)"
         }
       ]
     },
@@ -587,7 +653,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -609,10 +675,18 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
         },
+        {
+          "name": "operator",
+          "description": "Fixes the operator for the element's life: no menu and no button render, and every tuple carries it. The plural is the menu's whitelist; declaring both warns, the singular winning, and an unknown name warns and pins the filter's default. (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. (boolean)"
@@ -645,7 +719,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -667,10 +741,18 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
         },
+        {
+          "name": "operator",
+          "description": "Fixes the operator for the element's life: no menu and no button render, and every tuple carries it. The plural is the menu's whitelist; declaring both warns, the singular winning, and an unknown name warns and pins the filter's default. (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. (boolean)"
@@ -703,7 +785,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -725,10 +807,18 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
         },
+        {
+          "name": "operator",
+          "description": "Fixes the operator for the element's life: no menu and no button render, and every tuple carries it. The plural is the menu's whitelist; declaring both warns, the singular winning, and an unknown name warns and pins the filter's default. (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. (boolean)"
@@ -783,11 +873,11 @@
     },
     {
       "name": "ful-filter-text",
-      "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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -809,10 +899,22 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (boolean)"
         },
+        {
+          "name": "unsigned",
+          "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it. (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. (string)"
         },
+        {
+          "name": "operator",
+          "description": "Fixes the operator for the element's life: no menu and no button render, and every tuple carries it. The plural is the menu's whitelist; declaring both warns, the singular winning, and an unknown name warns and pins the filter's default. (string)"
+        },
+        {
+          "name": "sensitivity",
+          "description": "Fixes the case sensitivity for the element's life, on the operator's terms: the button leaves and every tuple carries it. (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. (boolean)"
@@ -844,8 +946,8 @@
       ]
     },
     {
-      "name": "ful-select",
-      "description": "A combobox backed by a loader that acts like a select: the field mirrors the label of a single selection, clicking anywhere on it toggles the dropdown, which opens highlighting the current selection, and Home, End, PageUp, PageDown and Alt+arrows navigate it. A multiple selection renders as ful-badge chips. Without src the slotted options are the vocabulary; with src the options are fetched once (method, POST by default, preload fetching them while upgrading, revision caching them in local storage) or asked per query under mode=chunked, the response shaped through the k-expr/l-expr/d-expr/m-expr expressions or a response-mapper component, and every key coerced as k-type declares. 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.",
+      "name": "ful-filter-in",
+      "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 value is an array whether one key was chosen or several, an empty selection contributing nothing rather than an empty array. It picks one key unless multiple is declared, as a ful-select does.",
       "attributes": [
         {
           "name": "name",
@@ -857,15 +959,93 @@
         },
         {
           "name": "k-type",
-          "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or bool. (string)"
+          "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or boolean. (string)"
+        },
+        {
+          "name": "mode",
+          "description": "chunked asks the endpoint per query instead of fetching the vocabulary once, for a list too large to hold. (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. (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. (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. (string)"
+        },
+        {
+          "name": "l-expr",
+          "description": "The expression yielding an option's label, evaluated against each row of the response. (string)"
+        },
+        {
+          "name": "d-expr",
+          "description": "The expression yielding the rows from the response body; the body itself when absent. (string)"
+        },
+        {
+          "name": "m-expr",
+          "description": "The expression yielding an option's metadata, evaluated against each row; the whole row when absent. (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. (string)"
+        },
+        {
+          "name": "operator",
+          "description": "A fixed operator sent in front of the chosen keys, for the field a compare reads rather than a set: absent the value is the bare array an InEnum or an InList takes, present it is [operator, ...keys]. No menu is rendered either way, the operator being the author naming the server's comparison rather than a choice offered to whoever is filtering. The criterion reports it, so a chip can show it. (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. (boolean)"
+        },
+        {
+          "name": "readonly",
+          "description": "Renders the control but does not let it be edited. A readonly field still contributes its value to the form. (boolean)"
+        },
+        {
+          "name": "required",
+          "description": "Marks the field as required for assistive technologies and shows the required marker on its label. (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. (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. (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). (boolean)"
         },
         {
           "name": "src",
-          "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory. (string)"
+          "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory. Stays live: writing it builds the loader again and reloads as reload() does, dropping a selected key the new vocabulary does not know. (string)"
         },
         {
           "name": "method",
-          "description": "The method the vocabulary is fetched with; POST when absent. (string)"
+          "description": "The method the vocabulary is fetched with; POST when absent. Stays live, as src does. (string)"
+        }
+      ]
+    },
+    {
+      "name": "ful-select",
+      "description": "A combobox backed by a loader that acts like a select: the field mirrors the label of a single selection, clicking anywhere on it toggles the dropdown, which opens highlighting the current selection, and Home, End, PageUp, PageDown and Alt+arrows navigate it. A multiple selection renders as ful-badge chips. Without src the slotted options are the vocabulary; with src the options are fetched once (method, POST by default, preload fetching them while upgrading, revision caching them in local storage) or asked per query under mode=chunked, the response shaped through the k-expr/l-expr/d-expr/m-expr expressions or a response-mapper component, and every key coerced as k-type declares. 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": "name",
+          "description": "The field name the surrounding form submits the selection under. (string)"
+        },
+        {
+          "name": "loader",
+          "description": "The registered component name the select loads its vocabulary through; loaders:select when absent. (string)"
+        },
+        {
+          "name": "k-type",
+          "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or boolean. (string)"
         },
         {
           "name": "mode",
@@ -877,7 +1057,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. (string)"
+          "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. (string)"
         },
         {
           "name": "k-expr",
@@ -913,7 +1093,7 @@
         },
         {
           "name": "value",
-          "description": "The selected keys, comma separated, whether or not the select is multiple. A key given here is trimmed and cannot contain a comma; assign such a key through the property instead. The property answers a key for a single select and an array for a multiple one. (string)"
+          "description": "The selected keys, comma separated, whether or not the select is multiple. A key given here is trimmed and cannot contain a comma; assign such a key through the property instead. The property answers a key for a single select and an array for a multiple one. A single select reads a present but empty attribute as the empty key, the one an <option value=\"\"> carries, where an absent attribute means no selection; a multiple select reads it as no keys. (string)"
         },
         {
           "name": "multiple",
@@ -922,12 +1102,20 @@
         {
           "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). (boolean)"
+        },
+        {
+          "name": "src",
+          "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory. Stays live: writing it builds the loader again and reloads as reload() does, dropping a selected key the new vocabulary does not know. (string)"
+        },
+        {
+          "name": "method",
+          "description": "The method the vocabulary is fetched with; POST when absent. Stays live, as src does. (string)"
         }
       ]
     },
     {
       "name": "ful-dropdown",
-      "description": "The options popup of a ful-select, with a localized no-results message when the search matches nothing. Rarely used on its own.",
+      "description": "The options popup of a ful-select, with a localized no-results message when the search matches nothing. An entry whose metadata.disabled is truthy is refused: its row carries aria-disabled and metadata.reason as its title, the arrows and Home/End walk past it, and a click on it changes nothing. Rarely used on its own.",
       "attributes": [
         {
           "name": "listbox",