@adia-ai/web-components 0.8.47 → 0.8.48

package/components/table-footer/table-footer.yaml

@@ -55,14 +55,22 @@ props:
       range label's position when supplied). Named identically to
       table-toolbar-ui's [range-total] and table-ui's own [range-total]
       (gh#1754, ADR-0082) and deliberately NOT `total` (pagination-ui's
-      `total` is total PAGES — the ADR-0063 B5 collision rule). When this
-      attribute is unset, the footer derives it from the resolved target
-      via a two-branch ladder (REQ-W-006, amended 0.2.0/ADR-0082):
+      `total` is total PAGES — the ADR-0063 B5 collision rule). Explicit
+      range-total="?" (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-
+      total state — cursor/hasMore server paging with no known row count
+      yet: the range label renders "Showing X–Y" with no "of N", and the
+      pager stays in has-more mode (next enabled) rather than hiding —
+      distinct from both "loading" (attribute absent) and "confirmed empty"
+      (range-total="0"). Resolves to the normal finite behavior the moment
+      a real number replaces the "?". When this attribute is unset, the
+      footer derives it from the resolved target via a two-branch ladder
+      (REQ-W-006, amended 0.2.0/ADR-0082):
       (1) the target's own [range-total] attribute, when present — the
       table-authoritative SERVER mode (gh#1754 Shape 1's second lawful
-      composition); the identity rule: the footer's range-total derives
-      from the table's range-total, never the table's filteredCount, and
-      this branch wins even when the target's [paginate] is also > 0;
+      composition; the target's own "?" carries through identically); the
+      identity rule: the footer's range-total derives from the table's
+      range-total, never the table's filteredCount, and this branch wins
+      even when the target's [paginate] is also > 0;
       (2) otherwise, when the target has [paginate] > 0, CLIENT mode: the
       target's filtered row count (search + column filters applied, before
       pagination). Refreshes on the target's `page` / `filter-change` /
@@ -71,9 +79,34 @@ props:
       on the target without an accompanying page move — emits no event;
       either re-set this footer's own attributes after such a change, or
       accept staleness until the target's next event.
+    type: [number, string]
+    default: 0
+    reflect: true
+  range-of:
+    description: >-
+      gh#1877, ADR-0082 Amendment — secondary whole-set total for the
+      "filtered-of-whole" shape: a client-side facet narrows [range-total]
+      (a filtered count) while range-of names the unfiltered set size, e.g.
+      "Showing 1–4 of 4 traversals (6 total)". Appends "(of <range-of>
+      total)" onto the normal finite range text; unset (the default)
+      changes nothing. Never applies while [range-total] is absent
+      (loading) or "?" (open/unproven) — there's no finite range text to
+      append onto yet. Named identically on table-toolbar-ui (ADR-0082
+      §"same name on both companions").
     type: number
     default: 0
     reflect: true
+  range-noun:
+    description: >-
+      gh#1877, ADR-0082 Amendment — optional per-slice noun appended after
+      the range total ("of 80 users") so consumers stop hand-painting the
+      noun themselves. Applies in both the normal finite range text and the
+      open/unproven-total text ("Showing 51–100 users" with no "of N").
+      Unset (the default) changes nothing. Named identically on
+      table-toolbar-ui (ADR-0082 §"same name on both companions").
+    type: string
+    default: ""
+    reflect: true
   siblings:
     description: Passed through to the composed pagination-ui's own [siblings] (page-number window size on each side of the current page).
     type: number
@@ -166,6 +199,13 @@ a2ui:
       range label's own position, without a layout shift versus the normal
       range text. Only fires on an EXPLICIT range-total="0" — omitting
       range-total entirely (loading) never shows it.
+    - >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server paging (no
+      server-reported row count, only "more rows exist or not") sets
+      [range-total="?"] instead of a real number: the range label reads
+      "Showing 51–100" with no "of N", and the pager keeps `next` enabled
+      until a later response supplies a real [range-total], at which point
+      the footer renders the normal finite text automatically.
 anti_patterns:
   - wrong: '<table-footer-ui range-start="1" range-end="10" range-total="128"></table-footer-ui>'
     why: >-
@@ -185,6 +225,17 @@ examples:
         {"id": "tests", "component": "Table", "raw": true},
         {"id": "ftr", "component": "TableFooter", "for": "tests", "page": 1, "page-size": 10, "range-total": 128}
       ]
+  - name: table-footer-open-total
+    description: >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server mode with no known
+      row count yet: [range-total="?"] renders "Showing 1–50 subscriptions"
+      (via [range-noun]) with `next` kept enabled until a real total resolves.
+    a2ui: >-
+      [
+        {"id": "root", "component": "Column", "gap": "0", "children": ["subs", "ftr"]},
+        {"id": "subs", "component": "Table", "raw": true},
+        {"id": "ftr", "component": "TableFooter", "for": "subs", "page": 1, "page-size": 50, "range-total": "?", "range-noun": "subscriptions"}
+      ]
   - name: table-footer-client-mode
     description: Client-mode footer bound to a [paginate]d table-ui with its own internal pager suppressed via [no-pager].
     a2ui: >-

package/components/table-toolbar/table-toolbar.a2ui.json

@@ -70,14 +70,27 @@
       "type": "number",
       "default": 0
     },
+    "rangeNoun": {
+      "description": "gh#1877, ADR-0082 Amendment — optional per-slice noun appended after the range total (\"of 80 users\") so consumers stop hand-painting the noun themselves. Applies in both the normal finite range summary and the open/unproven-total summary (\"Showing 51–100 users\" with no \"of N\"). Unset (the default) changes nothing. Named identically to table-footer-ui's own [range-noun] (ADR-0082 §\"same name on both companions\").",
+      "type": "string",
+      "default": ""
+    },
+    "rangeOf": {
+      "description": "gh#1877, ADR-0082 Amendment — secondary whole-set total for the \"filtered-of-whole\" shape: a client-side facet narrows [rangeTotal] (a filtered count) while rangeOf names the unfiltered set size, e.g. \"Showing 1–4 of 4 traversals (6 total)\". Appends \"(of <rangeOf> total)\" onto the normal finite range summary; unset (the default) changes nothing. Never applies while the summary is in its open (\"?\") or opted-out (all-zero) state. Named identically to table-footer-ui's own [range-of] (ADR-0082 §\"same name on both companions\").",
+      "type": "number",
+      "default": 0
+    },
     "rangeStart": {
       "description": "1-indexed first row number of the current page, for the \"Showing X–Y of N\" range summary (e.g. `1` in \"Showing 1–25 of 320\"). Renders alongside — never in place of — [text]/[count]; the range summary is its own cluster, independent of the title cluster. All three of rangeStart/rangeEnd/rangeTotal must be set (> 0) for the summary to render; omit all three (the default) to opt out entirely.",
       "type": "number",
       "default": 0
     },
     "rangeTotal": {
-      "description": "Total row count across all pages, for the range summary (e.g. `320` in \"Showing 1–25 of 320\"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart.",
-      "type": "number",
+      "description": "Total row count across all pages, for the range summary (e.g. `320` in \"Showing 1–25 of 320\"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart. Explicit range-total=\"?\" (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-total state — cursor/hasMore server paging with no known row count yet: the summary reads \"Showing X–Y\" with no \"of N\", requiring only [range-start]/[range-end] (> 0) to render, not rangeTotal too. Resolves to the normal finite summary the moment a real number replaces the \"?\". Named identically to table-footer-ui's own [range-total] (ADR-0082 §\"same name on both companions\").",
+      "type": [
+        "number",
+        "string"
+      ],
       "default": 0
     },
     "size": {
@@ -107,6 +120,11 @@
       "type": "string",
       "default": ""
     },
+    "titleAlways": {
+      "description": "Opt out of the scope-reconciliation title hide: by default, a filled [slot=\"scope\"] region (a select/menu whose own displayed value already names the entity being listed) hides the separate [text]/[count] title cluster next to it, since together they'd say the same thing twice. Set [title-always] to keep the title cluster visible alongside a filled scope slot — e.g. a scope select PLUS an explicit text/count title on the same row (gh#1879).",
+      "type": "boolean",
+      "default": false
+    },
     "variant": {
       "description": "Toolbar visual variant. `default` renders bare on parent surface; `card` adds the same chrome as a card-ui header.",
       "type": "string",
@@ -179,6 +197,11 @@
         "description": "The ratified adiav2 list-page toolbar row (ADIA2-9123, gh#1649): scope menu, range summary, app-owned Filter/Columns triggers (their own filter drawer, not the native popovers — [no-filter]/[no-columns]/ [no-sort]/[no-search] drop the native affordances), page-size select, and a primary CTA — [slot=\"actions-leading\"] carries the Filter/Columns triggers so they land BEFORE the page-size select, while [slot=\"actions\"] carries the CTA so it lands after.",
         "a2ui": "[\n  {\"id\": \"root\", \"component\": \"Column\", \"gap\": \"3\", \"children\": [\"bar\", \"card\"]},\n  {\"id\": \"bar\", \"component\": \"TableToolbar\", \"for\": \"accounts\", \"no-filter\": true, \"no-sort\": true, \"no-columns\": true, \"no-search\": true, \"range-start\": 1, \"range-end\": 25, \"range-total\": 320, \"page-size\": 25, \"page-size-options\": [10, 25, 50, 100], \"children\": [\"btn-filter\", \"btn-columns\", \"btn-new\"]},\n  {\"id\": \"btn-filter\", \"component\": \"Button\", \"text\": \"Filter\", \"variant\": \"ghost\", \"slot\": \"actions-leading\"},\n  {\"id\": \"btn-columns\", \"component\": \"Button\", \"text\": \"Columns\", \"variant\": \"ghost\", \"slot\": \"actions-leading\"},\n  {\"id\": \"btn-new\", \"component\": \"Button\", \"text\": \"New account\", \"variant\": \"primary\", \"slot\": \"actions\"},\n  {\"id\": \"card\", \"component\": \"Card\", \"children\": [\"sec\"]},\n  {\"id\": \"sec\", \"component\": \"Section\", \"bleed\": true, \"children\": [\"tbl\"]},\n  {\"id\": \"tbl\", \"component\": \"Table\", \"id\": \"accounts\", \"sortable\": true, \"raw\": true}\n]",
         "name": "adiav2-list-page-toolbar-row"
+      },
+      {
+        "description": "gh#1877, ADR-0082 Amendment — cursor/hasMore server paging with no known row count yet: [range-total=\"?\"] renders \"Showing 1–50 subscriptions\" (via [range-noun]) with no \"of N\", resolving to the normal finite summary once a real total arrives.",
+        "a2ui": "[\n  {\"id\": \"root\", \"component\": \"Column\", \"gap\": \"3\", \"children\": [\"bar\", \"card\"]},\n  {\"id\": \"bar\", \"component\": \"TableToolbar\", \"for\": \"subs\", \"range-start\": 1, \"range-end\": 50, \"range-total\": \"?\", \"range-noun\": \"subscriptions\"},\n  {\"id\": \"card\", \"component\": \"Card\", \"children\": [\"sec\"]},\n  {\"id\": \"sec\", \"component\": \"Section\", \"bleed\": true, \"children\": [\"tbl\"]},\n  {\"id\": \"tbl\", \"component\": \"Table\", \"id\": \"subs\", \"raw\": true}\n]",
+        "name": "table-toolbar-open-total"
       }
     ],
     "keywords": [

package/components/table-toolbar/table-toolbar.class.js

@@ -172,6 +172,12 @@ export class UITableToolbar extends UIElement {
     rangeStart:  { type: Number,  default: 0,          reflect: true, attribute: 'range-start' },
     rangeEnd:    { type: Number,  default: 0,          reflect: true, attribute: 'range-end' },
     rangeTotal:  { type: Number,  default: 0,          reflect: true, attribute: 'range-total' },
+    // gh#1877/ADR-0082 Amendment — same-name mirrors of table-footer-ui's
+    // own range-of/range-noun (ADR-0082 §"same name on both companions"):
+    // range-of is the secondary whole-set total ("filtered-of-whole"),
+    // range-noun the optional per-slice noun. Both presence-gated.
+    rangeOf:     { type: Number,  default: 0,          reflect: true, attribute: 'range-of' },
+    rangeNoun:   { type: String,  default: '',         reflect: true, attribute: 'range-noun' },
     pageSize:    { type: Number,  default: 0,          reflect: true, attribute: 'page-size' },
     noFilter:    { type: Boolean, default: false,      reflect: true, attribute: 'no-filter' },
     noSort:      { type: Boolean, default: false,      reflect: true, attribute: 'no-sort' },
@@ -181,6 +187,13 @@ export class UITableToolbar extends UIElement {
     // above. Pure, absolute OR: see #updateControlVisibility(), which is the
     // single place that combines chromeOnly with each granular no-* value.
     chromeOnly:  { type: Boolean, default: false,      reflect: true, attribute: 'chrome-only' },
+    // gh#1879 — opt-out for the scope-reconciliation title hide
+    // (table-toolbar.css's `:scope:not([title-always]):has([data-scope]:not(:empty))
+    // [data-title] { display: none; }`). Presence-only: the CSS rule reads
+    // the reflected attribute directly, so no JS branch is needed here
+    // beyond the standard Boolean reflect declaration (same shape as
+    // noFilter/noSort/noColumns/noSearch/chromeOnly above).
+    titleAlways: { type: Boolean, default: false,      reflect: true, attribute: 'title-always' },
     placeholder: { type: String,  default: 'Search...', reflect: false },
     variant:     { type: String,  default: 'default',  reflect: true },
     // ADR-0076 REQ-O-001 — explicit compaction-stage override. Unset (the
@@ -342,7 +355,7 @@ export class UITableToolbar extends UIElement {
   // value one, so it needs the raw attribute callback, not the signal diff.
   attributeChangedCallback(name, oldVal, newVal) {
     super.attributeChangedCallback(name, oldVal, newVal);
-    if (name === 'range-total') this.#updateSummary();
+    if (name === 'range-total' || name === 'range-of' || name === 'range-noun') this.#updateSummary();
     // ADR-0076 REQ-M-005 — the SECOND of the two triggers `data-stage-
     // resolved` must react to: a live resize (the ResizeObserver callback
     // above) AND a `stage` attribute change alone, with no resize needed.
@@ -849,13 +862,45 @@ export class UITableToolbar extends UIElement {
     const end = Number(this.rangeEnd) || 0;
     const total = Number(this.rangeTotal) || 0;
 
+    // gh#1877/ADR-0082 Amendment — same open/unproven-total discipline as
+    // table-footer-ui's own #draw(): NOT keyed on the raw attribute
+    // string. rangeTotal is a Number-typed reflected prop, so
+    // range-total="?" parses via `+"?"` → NaN and the property setter's
+    // own reflect() immediately rewrites the DOM attribute to the literal
+    // string "NaN" (core/element.js) — getAttribute('range-total') would
+    // read "NaN", never "?". The coerced PROPERTY still holds NaN stably
+    // (Object.is(NaN, NaN) is true, so the reflect's re-parse never
+    // re-writes it), and that's what tells "unknown yet" apart from a
+    // confirmed range-total="0" (a finite 0).
+    const rangeOpen = !Number.isFinite(Number(this.rangeTotal));
+    // gh#1877/ADR-0082 Amendment — additive suffixes onto the normal
+    // finite "of N" text; range-of (secondary whole-set total) never
+    // applies to the open-total branch (no finite total to append against).
+    const hasRangeOf = this.hasAttribute('range-of');
+    const rangeOfVal = hasRangeOf ? (Number(this.rangeOf) || 0) : 0;
+    const rangeOfSuffix = hasRangeOf && rangeOfVal > 0 ? ` (of ${rangeOfVal} total)` : '';
+    const nounSuffix = this.rangeNoun ? ` ${this.rangeNoun}` : '';
+
+    if (rangeOpen && start > 0 && end > 0) {
+      // REQ-open (gh#1877/ADR-0082 Amendment) — "Showing X–Y" with no
+      // "of N"; the short-form mirrors it minus the "Showing " prefix,
+      // same paired-population discipline as the finite branch below.
+      if (text) text.textContent = `Showing ${start}–${end}${nounSuffix}`;
+      if (text) text.hidden = false;
+      if (compact) compact.textContent = `${start}–${end}`;
+      if (compact) compact.hidden = false;
+      if (empty) empty.hidden = true;
+      summary.hidden = false;
+      return;
+    }
+
     if (start > 0 && end > 0 && total > 0) {
       // Normal range text — always wins over the empty slot (AC-014).
       // Both the full ("Showing X–Y of N") and short-form ("X–Y/N", ADR-0076
       // REQ-S-003) strings are populated together — which one paints is a
       // pure CSS decision (icon-only @container rule / [stage] pin), never
       // a JS branch (REQ-M-002).
-      if (text) text.textContent = `Showing ${start}–${end} of ${total}`;
+      if (text) text.textContent = `Showing ${start}–${end} of ${total}${nounSuffix}${rangeOfSuffix}`;
       if (text) text.hidden = false;
       if (compact) compact.textContent = `${start}–${end}/${total}`;
       if (compact) compact.hidden = false;

package/components/table-toolbar/table-toolbar.css

@@ -330,8 +330,12 @@
      prop; this reads what's already in the DOM, same `:has()` idiom the
      [data-summary]/[data-page-size] reconciliation above already uses).
      A consumer wanting BOTH visible can still override with normal CSS
-     specificity — this isn't a hard mode switch, just the default. */
-  :scope:has([data-scope]:not(:empty)) [data-title] {
+     specificity — this isn't a hard mode switch, just the default.
+     [title-always] (gh#1879) is the declared opt-out for that same case:
+     a consumer wanting BOTH the scope select AND the explicit text/count
+     title visible together sets the attribute instead of reaching for an
+     app-side CSS override. */
+  :scope:not([title-always]):has([data-scope]:not(:empty)) [data-title] {
     display: none;
   }
 

package/components/table-toolbar/table-toolbar.d.ts

@@ -46,16 +46,22 @@ export class UITableToolbar extends UIElement {
   placeholder: string;
   /** 1-indexed last row number of the current page, for the range summary (e.g. `25` in "Showing 1–25 of 320"). See rangeStart. */
   rangeEnd: number;
+  /** gh#1877, ADR-0082 Amendment — optional per-slice noun appended after the range total ("of 80 users") so consumers stop hand-painting the noun themselves. Applies in both the normal finite range summary and the open/unproven-total summary ("Showing 51–100 users" with no "of N"). Unset (the default) changes nothing. Named identically to table-footer-ui's own [range-noun] (ADR-0082 §"same name on both companions"). */
+  rangeNoun: string;
+  /** gh#1877, ADR-0082 Amendment — secondary whole-set total for the "filtered-of-whole" shape: a client-side facet narrows [rangeTotal] (a filtered count) while rangeOf names the unfiltered set size, e.g. "Showing 1–4 of 4 traversals (6 total)". Appends "(of <rangeOf> total)" onto the normal finite range summary; unset (the default) changes nothing. Never applies while the summary is in its open ("?") or opted-out (all-zero) state. Named identically to table-footer-ui's own [range-of] (ADR-0082 §"same name on both companions"). */
+  rangeOf: number;
   /** 1-indexed first row number of the current page, for the "Showing X–Y of N" range summary (e.g. `1` in "Showing 1–25 of 320"). Renders alongside — never in place of — [text]/[count]; the range summary is its own cluster, independent of the title cluster. All three of rangeStart/rangeEnd/rangeTotal must be set (> 0) for the summary to render; omit all three (the default) to opt out entirely. */
   rangeStart: number;
-  /** Total row count across all pages, for the range summary (e.g. `320` in "Showing 1–25 of 320"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart. */
-  rangeTotal: number;
+  /** Total row count across all pages, for the range summary (e.g. `320` in "Showing 1–25 of 320"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart. Explicit range-total="?" (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-total state — cursor/hasMore server paging with no known row count yet: the summary reads "Showing X–Y" with no "of N", requiring only [range-start]/[range-end] (> 0) to render, not rangeTotal too. Resolves to the normal finite summary the moment a real number replaces the "?". Named identically to table-footer-ui's own [range-total] (ADR-0082 §"same name on both companions"). */
+  rangeTotal: number | string;
   /** Toolbar scale, via sizing.css's universal [size="sm|md|lg"] ambient tokens. Not table-toolbar-specific chrome — the same attribute that scales any component. Set it once on the toolbar instead of on each slotted scope/actions-leading/actions control individually; anything slotted with no [size] of its own inherits the ambient value. Default (empty) = md. */
   size: 'sm' | 'md' | 'lg';
   /** Explicit compaction-stage override (ADR-0076). Unset (the default, empty string) means auto-snap: the toolbar's own inline-size container query picks the nearest stage from its live width against the three --table-toolbar-bp-* breakpoints, snapping discretely, never interpolating. Setting stage explicitly pins that stage's rendering regardless of the container's actual width — overriding the container query, mirroring chart-ui's ratio override shape. Primary use: visual-eval fixtures that need a deterministic stage without resizing a real container, and a consumer embedding the toolbar inside a known-narrow panel who wants to skip auto-detection entirely. All four stages' CSS is now live (ADR-0076): search-tight steps the search field down (step 2); icon-only drops control labels and compacts/hides the range summary (steps 3+4); overflow collapses Filter/Sort/Columns into one "More" trigger routed through the same menu-ui/menu-item-ui pattern used elsewhere in the corpus (step 5). The resolved stage — the pin if set, otherwise the live width classification — also reflects onto the host as `data-stage-resolved` (step 7, informational only, mirrors chart-ui's `data-ratio-resolved` convention — never drives table-toolbar's own rendering, which stays 100% CSS-driven). */
   stage: '' | 'full' | 'search-tight' | 'icon-only' | 'overflow';
   /** Title text shown on the left. */
   text: string;
+  /** Opt out of the scope-reconciliation title hide: by default, a filled [slot="scope"] region (a select/menu whose own displayed value already names the entity being listed) hides the separate [text]/[count] title cluster next to it, since together they'd say the same thing twice. Set [title-always] to keep the title cluster visible alongside a filled scope slot — e.g. a scope select PLUS an explicit text/count title on the same row (gh#1879). */
+  titleAlways: boolean;
   /** Toolbar visual variant. `default` renders bare on parent surface; `card` adds the same chrome as a card-ui header. */
   variant: 'default' | 'card';
 

package/components/table-toolbar/table-toolbar.examples.md

@@ -3,11 +3,13 @@
 ## Wiring
 
 ```html
-<table-toolbar-ui for="members" text="All employees" count="32"></table-toolbar-ui>
 <card-ui>
-  <section-ui bleed>
-    <table-ui id="members" sortable raw>…</table-ui>
-  </section-ui>
+  <header>
+    <table-toolbar-ui for="members" text="All employees" count="32"></table-toolbar-ui>
+  </header>
+  <section bleed>
+    <table-ui id="members" sortable>…</table-ui>
+  </section>
 </card-ui>
 ```
 

package/components/table-toolbar/table-toolbar.yaml

@@ -88,11 +88,45 @@ props:
       in "Showing 1–25 of 320"). Distinct from pagination-ui's `total`
       (total PAGES) — this is total ROWS; deliberately not spelled `total`
       to avoid that cross-sibling name collision (ADR-0063 B5). See
-      rangeStart.
-    type: number
+      rangeStart. Explicit range-total="?" (gh#1877, ADR-0082 Amendment) is
+      the OPEN/unproven-total state — cursor/hasMore server paging with no
+      known row count yet: the summary reads "Showing X–Y" with no "of N",
+      requiring only [range-start]/[range-end] (> 0) to render, not
+      rangeTotal too. Resolves to the normal finite summary the moment a
+      real number replaces the "?". Named identically to table-footer-ui's
+      own [range-total] (ADR-0082 §"same name on both companions").
+    type: [number, string]
     default: 0
     reflect: true
     attribute: range-total
+  rangeOf:
+    description: >-
+      gh#1877, ADR-0082 Amendment — secondary whole-set total for the
+      "filtered-of-whole" shape: a client-side facet narrows [rangeTotal]
+      (a filtered count) while rangeOf names the unfiltered set size, e.g.
+      "Showing 1–4 of 4 traversals (6 total)". Appends "(of <rangeOf>
+      total)" onto the normal finite range summary; unset (the default)
+      changes nothing. Never applies while the summary is in its open
+      ("?") or opted-out (all-zero) state. Named identically to
+      table-footer-ui's own [range-of] (ADR-0082 §"same name on both
+      companions").
+    type: number
+    default: 0
+    reflect: true
+    attribute: range-of
+  rangeNoun:
+    description: >-
+      gh#1877, ADR-0082 Amendment — optional per-slice noun appended after
+      the range total ("of 80 users") so consumers stop hand-painting the
+      noun themselves. Applies in both the normal finite range summary and
+      the open/unproven-total summary ("Showing 51–100 users" with no "of
+      N"). Unset (the default) changes nothing. Named identically to
+      table-footer-ui's own [range-noun] (ADR-0082 §"same name on both
+      companions").
+    type: string
+    default: ""
+    reflect: true
+    attribute: range-noun
   pageSize:
     description: >-
       Current rows-per-page value, shown as the selected option in the
@@ -190,6 +224,19 @@ props:
     default: false
     reflect: true
     attribute: chrome-only
+  titleAlways:
+    description: >-
+      Opt out of the scope-reconciliation title hide: by default, a filled
+      [slot="scope"] region (a select/menu whose own displayed value already
+      names the entity being listed) hides the separate [text]/[count]
+      title cluster next to it, since together they'd say the same thing
+      twice. Set [title-always] to keep the title cluster visible alongside
+      a filled scope slot — e.g. a scope select PLUS an explicit
+      text/count title on the same row (gh#1879).
+    type: boolean
+    default: false
+    reflect: true
+    attribute: title-always
   placeholder:
     description: Placeholder text for the search input.
     type: string
@@ -343,13 +390,15 @@ a2ui:
       update the table.
     - >-
       Use [slot="scope"] for a leading scope/view switcher (an org's
-      teams, a saved view) rendered before [text]/[count]. Use
-      [range-start] / [range-end] / [range-total] together for a
-      "Showing X–Y of N" summary — it renders independently of, and
-      alongside, [text]/[count], never in place of them. Use [page-size]
-      + [page-size-options] for a rows-per-page select; it applies
-      directly to the bound table's [paginate] prop the same way
-      filter/sort/columns changes apply directly to the target.
+      teams, a saved view) rendered before [text]/[count]. By default, a
+      filled scope slot hides the [text]/[count] title cluster (they'd
+      otherwise repeat the same entity name) — set [title-always] to keep
+      both visible together. Use [range-start] / [range-end] /
+      [range-total] together for a "Showing X–Y of N" summary — it renders
+      independently of, and alongside, [text]/[count], never in place of
+      them. Use [page-size] + [page-size-options] for a rows-per-page
+      select; it applies directly to the bound table's [paginate] prop the
+      same way filter/sort/columns changes apply directly to the target.
     - >-
       Use [slot="actions-leading"] (gh#1649) for app-owned trigger
       buttons that must land BEFORE the page-size select — e.g. custom
@@ -373,6 +422,17 @@ a2ui:
       normal "Showing X-Y of N" text (ADR-0076, REQ-E). Only fires on an
       EXPLICIT range-total="0" — omitting range-* entirely (loading) never
       shows it.
+    - >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server paging (no
+      server-reported row count) sets [range-total="?"] instead of a real
+      number: the summary reads "Showing 51–100" with no "of N" (needs only
+      [range-start]/[range-end] > 0 to render), resolving to the normal
+      finite summary once a real [range-total] arrives. Use [range-of] for
+      the separate "filtered-of-whole" shape (a filtered range-total plus a
+      secondary unfiltered-set total, e.g. "of 4 traversals (6 total)"),
+      and [range-noun] to stop hand-painting the per-slice noun ("of 80
+      users"). Same three attributes, same names, on table-footer-ui
+      (ADR-0082 §"same name on both companions").
     - >-
       A plain <button-ui> slotted into [slot="actions-leading"] (e.g. the
       app-owned Filter/Columns triggers above) already collapses to
@@ -420,6 +480,20 @@ examples:
         {"id": "sec", "component": "Section", "bleed": true, "children": ["tbl"]},
         {"id": "tbl", "component": "Table", "id": "accounts", "sortable": true, "raw": true}
       ]
+  - name: table-toolbar-open-total
+    description: >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server paging with no
+      known row count yet: [range-total="?"] renders "Showing 1–50
+      subscriptions" (via [range-noun]) with no "of N", resolving to the
+      normal finite summary once a real total arrives.
+    a2ui: >-
+      [
+        {"id": "root", "component": "Column", "gap": "3", "children": ["bar", "card"]},
+        {"id": "bar", "component": "TableToolbar", "for": "subs", "range-start": 1, "range-end": 50, "range-total": "?", "range-noun": "subscriptions"},
+        {"id": "card", "component": "Card", "children": ["sec"]},
+        {"id": "sec", "component": "Section", "bleed": true, "children": ["tbl"]},
+        {"id": "tbl", "component": "Table", "id": "subs", "raw": true}
+      ]
 keywords:
   - table-toolbar
   - data-grid

package/custom-elements.json

@@ -2089,7 +2089,7 @@
               "type": {
                 "text": "string"
               },
-              "description": "Chart 2.0 aspect-ratio bucket (ADR-0074). Unset (default) auto-snaps to the nearest of the three studied ratios by comparing the chart's own live box aspect against two midpoint boundaries (5:4 between 3:2/1:1, 4:5 between 1:1/2:3) — never interpolated; the resolved bucket reflects onto the host as `data-ratio-resolved`. Setting `ratio` explicitly pins that bucket regardless of the box's actual aspect, overriding the auto-snap. Orthogonal to `size` (overall scale) and `type`/`color` (ADR-0064's family axis) — this attribute lands the grammar + snap plumbing only; per-type studied renderings per bucket are later waves (gh#1624 plan steps 2-4)."
+              "description": "Chart 2.0 aspect-ratio bucket (ADR-0074). Unset (default) auto-snaps to the nearest of the three studied ratios by comparing the chart's own live box aspect against two midpoint boundaries (5:4 between 3:2/1:1, 4:5 between 1:1/2:3) — never interpolated; the resolved bucket reflects onto the host as `data-ratio-resolved`. Setting `ratio` explicitly pins that bucket regardless of the box's actual aspect, overriding the auto-snap. Orthogonal to `size` (overall scale) and `type`/`color` (ADR-0064's family axis) — per-type studied renderings per bucket shipped across Waves A-C (gh#1624 plan steps 2-4: radial-bar/gauge/segments/stacked-bar/grouped-bar/multi-line, funnel/treemap/sankey/composed) — all 18 types have dedicated per-ratio render paths."
             },
             {
               "name": "labels",
@@ -9965,11 +9965,26 @@
             },
             {
               "name": "range-total",
+              "type": {
+                "text": "[number, string]"
+              },
+              "default": "0",
+              "description": "Total ROWS across all pages. Absent (the default) means \"not yet known\" (loading) — never \"zero\"; both the range label and the pager stay hidden until this is set. Explicit range-total=\"0\" is the confirmed-empty state (pager hidden; the `empty` slot renders in the range label's position when supplied). Named identically to table-toolbar-ui's [range-total] and table-ui's own [range-total] (gh#1754, ADR-0082) and deliberately NOT `total` (pagination-ui's `total` is total PAGES — the ADR-0063 B5 collision rule). Explicit range-total=\"?\" (gh#1877, ADR-0082 Amendment) is the OPEN/unproven- total state — cursor/hasMore server paging with no known row count yet: the range label renders \"Showing X–Y\" with no \"of N\", and the pager stays in has-more mode (next enabled) rather than hiding — distinct from both \"loading\" (attribute absent) and \"confirmed empty\" (range-total=\"0\"). Resolves to the normal finite behavior the moment a real number replaces the \"?\". When this attribute is unset, the footer derives it from the resolved target via a two-branch ladder (REQ-W-006, amended 0.2.0/ADR-0082): (1) the target's own [range-total] attribute, when present — the table-authoritative SERVER mode (gh#1754 Shape 1's second lawful composition; the target's own \"?\" carries through identically); the identity rule: the footer's range-total derives from the table's range-total, never the table's filteredCount, and this branch wins even when the target's [paginate] is also > 0; (2) otherwise, when the target has [paginate] > 0, CLIENT mode: the target's filtered row count (search + column filters applied, before pagination). Refreshes on the target's `page` / `filter-change` / `sort` events in either branch. Widened named staleness edge: a programmatic `.data` swap on the target — or a `range-total` update on the target without an accompanying page move — emits no event; either re-set this footer's own attributes after such a change, or accept staleness until the target's next event."
+            },
+            {
+              "name": "range-of",
               "type": {
                 "text": "number"
               },
               "default": "0",
-              "description": "Total ROWS across all pages. Absent (the default) means \"not yet known\" (loading) — never \"zero\"; both the range label and the pager stay hidden until this is set. Explicit range-total=\"0\" is the confirmed-empty state (pager hidden; the `empty` slot renders in the range label's position when supplied). Named identically to table-toolbar-ui's [range-total] and table-ui's own [range-total] (gh#1754, ADR-0082) and deliberately NOT `total` (pagination-ui's `total` is total PAGES — the ADR-0063 B5 collision rule). When this attribute is unset, the footer derives it from the resolved target via a two-branch ladder (REQ-W-006, amended 0.2.0/ADR-0082): (1) the target's own [range-total] attribute, when present — the table-authoritative SERVER mode (gh#1754 Shape 1's second lawful composition); the identity rule: the footer's range-total derives from the table's range-total, never the table's filteredCount, and this branch wins even when the target's [paginate] is also > 0; (2) otherwise, when the target has [paginate] > 0, CLIENT mode: the target's filtered row count (search + column filters applied, before pagination). Refreshes on the target's `page` / `filter-change` / `sort` events in either branch. Widened named staleness edge: a programmatic `.data` swap on the target — or a `range-total` update on the target without an accompanying page move — emits no event; either re-set this footer's own attributes after such a change, or accept staleness until the target's next event."
+              "description": "gh#1877, ADR-0082 Amendment — secondary whole-set total for the \"filtered-of-whole\" shape: a client-side facet narrows [range-total] (a filtered count) while range-of names the unfiltered set size, e.g. \"Showing 1–4 of 4 traversals (6 total)\". Appends \"(of <range-of> total)\" onto the normal finite range text; unset (the default) changes nothing. Never applies while [range-total] is absent (loading) or \"?\" (open/unproven) — there's no finite range text to append onto yet. Named identically on table-toolbar-ui (ADR-0082 §\"same name on both companions\")."
+            },
+            {
+              "name": "range-noun",
+              "type": {
+                "text": "string"
+              },
+              "description": "gh#1877, ADR-0082 Amendment — optional per-slice noun appended after the range total (\"of 80 users\") so consumers stop hand-painting the noun themselves. Applies in both the normal finite range text and the open/unproven-total text (\"Showing 51–100 users\" with no \"of N\"). Unset (the default) changes nothing. Named identically on table-toolbar-ui (ADR-0082 §\"same name on both companions\")."
             },
             {
               "name": "siblings",
@@ -10083,11 +10098,26 @@
             },
             {
               "name": "range-total",
+              "type": {
+                "text": "[number, string]"
+              },
+              "default": "0",
+              "description": "Total row count across all pages, for the range summary (e.g. `320` in \"Showing 1–25 of 320\"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart. Explicit range-total=\"?\" (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-total state — cursor/hasMore server paging with no known row count yet: the summary reads \"Showing X–Y\" with no \"of N\", requiring only [range-start]/[range-end] (> 0) to render, not rangeTotal too. Resolves to the normal finite summary the moment a real number replaces the \"?\". Named identically to table-footer-ui's own [range-total] (ADR-0082 §\"same name on both companions\")."
+            },
+            {
+              "name": "range-of",
               "type": {
                 "text": "number"
               },
               "default": "0",
-              "description": "Total row count across all pages, for the range summary (e.g. `320` in \"Showing 1–25 of 320\"). Distinct from pagination-ui's `total` (total PAGES) — this is total ROWS; deliberately not spelled `total` to avoid that cross-sibling name collision (ADR-0063 B5). See rangeStart."
+              "description": "gh#1877, ADR-0082 Amendment — secondary whole-set total for the \"filtered-of-whole\" shape: a client-side facet narrows [rangeTotal] (a filtered count) while rangeOf names the unfiltered set size, e.g. \"Showing 1–4 of 4 traversals (6 total)\". Appends \"(of <rangeOf> total)\" onto the normal finite range summary; unset (the default) changes nothing. Never applies while the summary is in its open (\"?\") or opted-out (all-zero) state. Named identically to table-footer-ui's own [range-of] (ADR-0082 §\"same name on both companions\")."
+            },
+            {
+              "name": "range-noun",
+              "type": {
+                "text": "string"
+              },
+              "description": "gh#1877, ADR-0082 Amendment — optional per-slice noun appended after the range total (\"of 80 users\") so consumers stop hand-painting the noun themselves. Applies in both the normal finite range summary and the open/unproven-total summary (\"Showing 51–100 users\" with no \"of N\"). Unset (the default) changes nothing. Named identically to table-footer-ui's own [range-noun] (ADR-0082 §\"same name on both companions\")."
             },
             {
               "name": "page-size",
@@ -10152,6 +10182,14 @@
               "default": "false",
               "description": "Suppress all four native controls/search at once (filter, sort, columns, search) as additive sugar over noFilter/noSort/noColumns/ noSearch (ADR-0076, ADIA2-9123). Precedence is pure, absolute OR — while set, all four stay off regardless of any individual no-* attribute's own value, with no partial re-enable path; to re-enable one control, remove chrome-only entirely and set the other three no-* attributes explicitly instead. The four granular attributes are not deprecated or removed — they remain the independently-addressable shipped API; chrome-only never replaces them, it's a convenience preset on top."
             },
+            {
+              "name": "title-always",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opt out of the scope-reconciliation title hide: by default, a filled [slot=\"scope\"] region (a select/menu whose own displayed value already names the entity being listed) hides the separate [text]/[count] title cluster next to it, since together they'd say the same thing twice. Set [title-always] to keep the title cluster visible alongside a filled scope slot — e.g. a scope select PLUS an explicit text/count title on the same row (gh#1879)."
+            },
             {
               "name": "placeholder",
               "type": {
@@ -10337,10 +10375,10 @@
             {
               "name": "range-total",
               "type": {
-                "text": "number"
+                "text": "[number, string]"
               },
               "default": "0",
-              "description": "Total row count across ALL server pages (gh#1754, ADR-0082) — the table-authoritative server-mode data contract. Presence-gated: the attribute's PRESENCE, not its value, is the mode switch (checked via hasAttribute, never the coerced value alone — the same discipline table-footer-ui's own [range-total] ships). Absent (the default) means client mode: today's behavior exactly, [paginate] slices `.data` as always. Present with [paginate] > 0 means server mode: no local slicing (`.data` IS the current page and renders whole, after local search/sort/filter), the internal pager's page count becomes `max(1, ceil(range-total / paginate))` (one calc site, consolidated), and the internal page-reset sites (`data` set, `setFilter`, `clearFilters`) are suppressed so a fetch write-back never fights the pager back to page 0 — page state then moves only via pager interaction, the `footer-page` command, or `setState()`. The existing `page` event (0-based, unchanged) becomes the fetch trigger: the consumer listens for it, fetches that server page, and writes `.data` back. Explicit `range-total=\"0\"` is server-confirmed empty (pager hidden), never conflated with absent. With [paginate] absent/0, [range-total] is inert for this table's own rendering but stays readable by a bound table-footer-ui (REQ-W-006 branch 2) for its count-only label — see the footer-authoritative shape below, which remains lawful and is unaffected by this attribute. Named identically to table-toolbar-ui's and table-footer-ui's own [range-total] (rows, never `pagination-ui[total]`'s pages — the ADR-0063 B5 collision rule); a third instance of one name for one concept."
+              "description": "Total row count across ALL server pages (gh#1754, ADR-0082) — the table-authoritative server-mode data contract. Presence-gated: the attribute's PRESENCE, not its value, is the mode switch (checked via hasAttribute, never the coerced value alone — the same discipline table-footer-ui's own [range-total] ships). Absent (the default) means client mode: today's behavior exactly, [paginate] slices `.data` as always. Present with [paginate] > 0 means server mode: no local slicing (`.data` IS the current page and renders whole, after local search/sort/filter), the internal pager's page count becomes `max(1, ceil(range-total / paginate))` (one calc site, consolidated), and the internal page-reset sites (`data` set, `setFilter`, `clearFilters`) are suppressed so a fetch write-back never fights the pager back to page 0 — page state then moves only via pager interaction, the `footer-page` command, or `setState()`. The existing `page` event (0-based, unchanged) becomes the fetch trigger: the consumer listens for it, fetches that server page, and writes `.data` back. Explicit `range-total=\"0\"` is server-confirmed empty (pager hidden), never conflated with absent. With [paginate] absent/0, [range-total] is inert for this table's own rendering but stays readable by a bound table-footer-ui (REQ-W-006 branch 2) for its count-only label — see the footer-authoritative shape below, which remains lawful and is unaffected by this attribute. Named identically to table-toolbar-ui's and table-footer-ui's own [range-total] (rows, never `pagination-ui[total]`'s pages — the ADR-0063 B5 collision rule); a third instance of one name for one concept. Explicit `range-total=\"?\"` (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-total state — cursor/hasMore server paging with no known row count yet: still server mode (still presence-gated), but the internal pager's page count stays exactly one page ahead of wherever the pager currently sits (never a fixed ceil(...) total), keeping `next` enabled indefinitely instead of hiding the pager the way a confirmed `range-total=\"0\"` would. Resolves to the normal finite server-mode behavior the instant a real number replaces the \"?\" — every reader downstream (table-toolbar-ui, table-footer-ui) shares this same distinction. Note: since this prop is Number-typed and reflected, the framework's own attribute-reflection immediately rewrites the DOM attribute to the literal string \"NaN\" once \"?\" is parsed (`+\"?\"` → NaN, then stringified back onto the attribute) — the coerced numeric PROPERTY is what carries the open/unproven signal (non-finite), never a literal \"?\" surviving as the live DOM attribute value."
             },
             {
               "name": "filteredCount",