bitboss-ui 3.0.0-beta.51 → 3.0.0-beta.52

package/bin/bitboss-ui-mcp.mjs

@@ -2733,7 +2733,7 @@ function listChanges({
 							: compareVersions(a, b)
 				)
 			),
-			hint: 'Counts only. What breaks when you bump: list_changes({ since: "<the version you have>" }) — one line per change; coming from v2: since: "2". One component: { component: "BbSelect" }. Full rows: detail: "rows".',
+			hint: 'Counts only. What a bump breaks: list_changes({ since: "<your version>" }), one line per change; from v2: since: "2". One component: { component: "BbSelect" }. Full rows: detail: "rows".',
 		};
 	}
 

package/dist/ai/BbTable.md

@@ -1471,7 +1471,9 @@ Add `selectable` for multi-select (`multiple` is the default) bound with
 `v-model` — the model **must** be an array in multiple mode (the table throws
 otherwise). With `item-value` set, the model holds ids rather than whole rows.
 Pass `selectable` a predicate (`(item) => boolean`) to gate specific rows: the
-excluded rows' controls disable and `toggleSelected` refuses them too.
+excluded rows' controls disable and `toggleSelected` refuses them too. Under
+`select-all` an excluded row stays unticked (select-all covers the rows the
+user can select); one the model names explicitly still shows ticked.
 
 To drive a toolbar that lives **outside** the table subtree, give the table an
 `id` and read `useBbTableContext(id).selected` — the handle mirrors the
@@ -2485,37 +2487,63 @@ details are open" — independent of selection. Clicking anywhere on a row
 toggles it: a new click replaces the previous highlight, and clicking the
 highlighted row clears it back to `null`. **Highlight is single by design** —
 one row is "the open one" — so bind a single item value, never an array. Two kinds of
-clicks are ignored on purpose: those inside interactive elements (links,
-buttons, inputs, labels keep their own semantics) and those ending a text
-selection (dragging to copy a cell must not mutate state).
+clicks are not row clicks: those starting on a control inside the row (a link,
+a button, an input, the select checkbox, any ARIA widget — they keep their own
+semantics) and those ending a text selection (dragging to copy a cell must not
+mutate state). Neither highlights the row nor emits `click:row`.
 
-**Highlight is opt-in, and the model's value is the switch.** Bind nothing and
-the mechanic is entirely off — a row click emits `click:row` and does nothing
+**Highlight is opt-in: it is on when it is bound.** Bind nothing and the
+mechanic is entirely off — a row click emits `click:row` and does nothing
 else: no class, no `aria-current`, no state. That matters because the table has
 nowhere to put a highlight it invents; a table that highlighted itself would
-drive a cursor the app can neither read nor clear.
-
-The switch reads the value, not the binding: **`undefined` means "never
-initialised" and keeps highlight off; `null` means "initialised and currently
-empty" and turns it on.** So initialise the model:
+drive a cursor the app can neither read nor clear. Bound means
+`v-model:highlighted` (whatever its value — `ref()` and `ref(null)` both mean
+"nothing open yet"), or `highlighted` provided through the shared context,
+which binds two ways just like the prop:
 
 ```ts
-const highlighted = ref(null); // ✅ connected
-const highlighted = ref(); // ❌ undefined — highlight stays off (warns in dev)
+const highlighted = ref<number | null>(null);
+useBbTableContext('invoices-table', { highlighted });
 ```
 
-A value seeded through the shared context counts exactly the same, and binds
-two ways just like the prop:
+**`highlightable` decides which rows a click may open.** `false` turns the
+click off for every row (a user without the privilege to open details), and a
+function of the row's item turns it off for some. A refused row ignores a
+click, Enter and `toggleHighlighted`, loses the pointer cursor highlightable
+rows get, and never clears the row that is open. It gates the user only: a
+value your code puts in `highlighted` (a deep link to a record) shows on a
+refused row too — the table reflects your state, it does not correct it, just
+as a `selectable`-refused row the model names stays ticked.
+
+Fetching the details belongs in a watcher on the model, not in `click:row`
+(the model also changes on the click that closes, on Enter, and from your own
+code). Abort the previous fetch when the highlight moves on, so a slow answer
+never paints over a newer one:
 
 ```ts
-const highlighted = ref(null);
-useBbTableContext('invoices-table', { highlighted });
+const openTaskId = ref<string | null>(null);
+watch(openTaskId, (id, _previous, onCleanup) => {
+	if (id === null) return taskStore.closeDetails();
+	const controller = new AbortController();
+	onCleanup(() => controller.abort());
+	void taskStore.showDetails(id, { signal: controller.signal });
+});
+```
+
+```vue
+<BbTable
+	v-model:highlighted="openTaskId"
+	:highlightable="can(Privilege.TASKS_SHOW)"
+	item-value="id"
+	:items="tasks"
+	:columns="columns"
+/>
 ```
 
-`click:row` is never gated — it fires on every row click whether or not
-highlight is connected, so listening for clicks costs you nothing. Calling
-`toggleHighlighted` from a cell slot on an unconnected table does nothing and
-warns once in dev.
+`click:row` is never gated by highlight — it fires on every row click whether
+or not highlight is bound or the row highlightable, so listening for clicks
+costs you nothing. Calling `toggleHighlighted` from a cell slot on an unbound
+table does nothing and warns once in dev.
 
 Highlight ships with a **default cursor**: the row gets `aria-current="true"`
 and the `bb-table__row--highlighted` class, and the shipped stylesheet
@@ -2743,7 +2771,11 @@ Row events: `click:row`, `dblclick:row` and `contextmenu:row` fire with
 `(event, item)` — the native event and **your record exactly as you passed it
 in `items`**, nothing else. No wrapper to unpack, no third argument; selection
 state is already yours through the `v-model`, and the row's value resolves
-from the record through `item-value` exactly as the models do. Reserve these
+from the record through `item-value` exactly as the models do. A click that
+starts on a control inside the row (the select checkbox, a link, a button, any
+ARIA widget) is the control's, not the row's: none of the three fires, so a
+cell's button needs no `@click.stop` and a right-click on a cell link keeps
+the browser's menu. Reserve these
 events for side effects that are not navigation —
 logging, opening a drawer (though `v-model:highlighted` usually covers that
 without any handler).
@@ -3994,7 +4026,8 @@ for a preset that fits any row type (never `<any>`), not an imported
 | `fixedLast` | `boolean \| undefined` | `false` |  | Sticks the `#<key>:last` row (a totals row) to the bottom of the scrollport. |
 | `fixedSelect` | `boolean \| undefined` | `false` |  | Pins the selection column to the left edge, `position: sticky`, in place. Data columns pin through `column.fixed`; this is the same feature for the structural column that has no definition to carry it. No effect unless the table is `selectable`. |
 | `headerRowClass` | `Classes \| undefined` |  |  | Defines the classes to be passed to the header row. |
-| `highlighted` | `any` | `undefined` |  | Used by `v-model:highlighted`: the one row the UI is about ("the row whose details are open"), a single item value or `null`. Opt-in: bind `ref(null)`, not `ref()`; unbound or `undefined`, a row click only emits `click:row`. The row gets `aria-current="true"` and a shipped tint. |
+| `highlightable` | `boolean \| ((item: Item) => boolean) \| undefined` | `undefined` |  | Which rows a click, Enter or `toggleHighlighted` may highlight: `false` for none, or a function of the row's item. Unset: every row, when `highlighted` is bound. A value the app sets still shows on a refused row. |
+| `highlighted` | `any` | `undefined` |  | Used by `v-model:highlighted`: the one row the UI is about ("the row whose details are open"), a single item value or `null`. Opt-in: bound, a row click highlights; unbound, it only emits `click:row`. The row gets `aria-current="true"` and a shipped tint. |
 | `id` | `string \| undefined` |  |  | Stable id for this table's width context. When omitted a unique id is generated. Nested tables use the nearest ancestor id to inherit widths. |
 | `inheritColumnWidths` | `string \| boolean \| undefined` |  |  | A nested table snaps its columns to an ancestor table's tracks: `true` = the nearest ancestor, a table `id` = that ancestor (when an intermediate table has a different column count). Off by default: a nested table sizes itself. |
 | `interactiveWhileLoading` | `boolean \| undefined` | `false` |  | Keeps the header and rows interactive while loading (by default they are `inert`: a refetch is about to replace them). For background refreshes that must not interrupt an open editor. |

package/dist/ai/changelog.json

@@ -1,7 +1,7 @@
 {
 	"schemaVersion": 3,
 	"library": "bitboss-ui",
-	"version": "3.0.0-beta.51",
+	"version": "3.0.0-beta.52",
 	"upgrade": "v2-to-v3",
 	"guide": "ai/guides/migration/v2-to-v3.md",
 	"legend": {
@@ -62,7 +62,8 @@
 		"3.0.0-beta.48",
 		"3.0.0-beta.49",
 		"3.0.0-beta.50",
-		"3.0.0-beta.51"
+		"3.0.0-beta.51",
+		"3.0.0-beta.52"
 	],
 	"unpublished": [
 		"3.0.0-alpha.2",
@@ -83,7 +84,7 @@
 	],
 	"summary": {
 		"renames": 220,
-		"behaviourBreaks": 188,
+		"behaviourBreaks": 190,
 		"bySurface": {
 			"prop": 15,
 			"option": 1,
@@ -5901,6 +5902,30 @@
 			"ruling": "owner 2026-10-08 (Q60.31 option B)",
 			"guide": "v2-to-v3.md § 6 item 56 + useBbFormField.md + validated-forms.md § validationMode",
 			"firstReleasedIn": "3.0.0-beta.51"
+		},
+		{
+			"id": "f328",
+			"kind": "behaviour",
+			"summary": "BbTable row events (`click:row`, `dblclick:row`, `contextmenu:row`) skip clicks on controls inside the row (select checkbox, link, button, ARIA widget); drop `@click.stop` guards",
+			"components": [
+				"BbTable"
+			],
+			"description": "BbTable: a click that starts on a control inside a row (the select checkbox, a link, a button, an input, any ARIA widget, contenteditable, [draggable]) emits no click:row, dblclick:row or contextmenu:row (they emitted for every click; the highlight already ignored them, now one rule for all, the row drag's); a click ending a text selection emits no click:row either. A cell button needs no @click.stop; a page guard on .bb-table__cell--select can go; a right-click on a cell link keeps the browser menu",
+			"ruling": "owner 2026-10-09 (progetto-32 report)",
+			"guide": "v2-to-v3.md § 6 item 57 + BbTable.guide.md § Row events",
+			"firstReleasedIn": "3.0.0-beta.52"
+		},
+		{
+			"id": "f329",
+			"kind": "behaviour",
+			"summary": "BbTable highlight is on when bound (any value; `undefined` no longer turns it off); new `highlightable` (bool or row function) gates which rows a click may highlight, app-set values still show",
+			"components": [
+				"BbTable"
+			],
+			"description": "BbTable highlight is on when BOUND (v-model:highlighted with any value, ref() included, or highlighted provided through useBbTableContext); the model's value no longer switches it (undefined was off, null on, with a dev warning for a bound undefined — gone). New highlightable (boolean | (item) => boolean; unset = on exactly when highlight is bound) gates which rows a click / Enter / toggleHighlighted may highlight; a refused row never clears the open one, and a value the app sets still shows on it. Highlightable rows get bb-table__row--highlightable and a pointer cursor. A page that kept highlight off by binding undefined moves to :highlightable=\"false\"",
+			"ruling": "owner 2026-10-09 (progetto-32, panel)",
+			"guide": "v2-to-v3.md § 6 item 58 + BbTable.guide.md § Row highlight + components/bb-table.md",
+			"firstReleasedIn": "3.0.0-beta.52"
 		}
 	]
 }