@ixfx/components 0.8.3 → 0.8.4

package/docs-user/dock.md

@@ -67,7 +67,10 @@ serialize with `saveLayout()` / `loadLayout()`, and render as
 `data-dock-name` on the leaf. Explicit leaf close still removes the stack.
 When a `tabs` drop empties a named stack into an *unnamed* one, the name
 (and its content rules) follows the panels to the merged leaf instead of
-leaving an empty placeholder behind.
+leaving an empty placeholder behind. Edge splits go the other way: a
+permitted split beside a named leaf yields a fresh *unnamed* sibling with no
+policy — set `allowEdgeSplit: false` (see Restrictions) to forbid the split
+entirely for strict named-area layouts.
 
 Spatial moves: `getNeighbours()` reports what sits above / below / left /
 right of a leaf (flat `{ name, path }` lists, most-overlapping first).
@@ -116,13 +119,24 @@ split resizes, and host resizes; handles are hidden during dock drags.
   `clearLeafContentRestrictions(name)` lifts both; `[]` seals (exclusive) or
   lifts (deny). Rules are host policy — kept across `loadLayout()`, never
   serialized; already-docked panels are grandfathered.
+- Leaf placement policy — `setLeafPlacementPolicy(name, policy)` is a superset
+  of the two calls above (`allowKinds` / `denyKinds`) plus `allowEdgeSplit`
+  (default `true`). `allowEdgeSplit: false` enforces **strict named-area
+  containment**: the edge drop zones *beside* that named leaf go inert, so a
+  panel cannot escape the area by splitting next to it. Fields merge into the
+  stored policy; `clearLeafPlacementPolicy(name)` resets. `getLeafPlacementPolicy(name)`
+  returns the resolved `{ allowKinds, denyKinds, allowEdgeSplit }`.
 
 A zone lights up only if every applicable rule allows it; disallowed zones
 are inert. Content rules govern tabbing *into* a leaf (`tabs` drops,
-`addPanel`, re-homing); edge splits beside the leaf stay allowed because they
-create a new sibling leaf. Programmatic fallbacks (`addPanel` without a
-target, external panels, leaf-close re-homing) use the first stack admitting
-the panel's kind.
+`addPanel`, re-homing). Edge splits beside a leaf stay allowed **unless** that
+named leaf's policy sets `allowEdgeSplit: false` — the gate is enforced on
+every placement route (pointer preview and drop, `queryDropTarget` /
+`previewExternalDrop`, `addPanel` with a split `op`). A *permitted* edge split
+still creates an **unnamed, unconstrained** leaf — the area policy is not
+propagated to it. Programmatic fallbacks (`addPanel` without a target,
+external panels, leaf-close re-homing) use the first stack admitting the
+panel's kind.
 
 ## Events
 
@@ -164,8 +178,16 @@ activatePanel(panelId: string): boolean
 getPanelIds(): string[]
 setLeafExclusiveContents(name: string, kinds: string[]): void
 setLeafDenyContents(name: string, kinds: string[]): void
+setLeafPlacementPolicy(name: string, policy: DockLeafPlacementPolicy): void
+type DockLeafPlacementPolicy = {
+  allowKinds?: string[];   // = setLeafExclusiveContents
+  denyKinds?: string[];    // = setLeafDenyContents
+  allowEdgeSplit?: boolean; // default true; false = strict named-area containment
+}                                // omitted fields merge into the stored policy
 clearLeafContentRestrictions(name: string): void
+clearLeafPlacementPolicy(name: string): void            // alias of the above
 getLeafContentRestrictions(name: string): DockLeafContentRules | null
+getLeafPlacementPolicy(name: string): DockLeafPlacementPolicyResolved | null
 getContainerNames(): string[]
 getContainer(name: string): { name: string; panels: string[]; active: string } | null
 getContainerPanels(name: string): string[]              // ids in tab order

package/docs-user/grid-list.md

@@ -149,9 +149,10 @@ grid.selectAll();
 grid.selectedItems;           // ReadonlySet<Element>
 ```
 
-Press-and-drag draws a marquee rectangle selecting every covered cell
-(automatic with `selection-mode="multiple"` or a multi `interaction-mode`;
-`disable-drag-select` opts out). See `docs-user/grid-list.md`.
+Press-and-drag on empty space between items draws a marquee rectangle selecting
+every covered cell — a press that starts on an item never starts a marquee, so
+it never fights an item drag or click (automatic with `selection-mode="multiple"`
+or a multi `interaction-mode`; `disable-drag-select` opts out).
 
 ### Key-based selection
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ixfx/components",
   "type": "module",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "packageManager": "pnpm@10.0.0",
   "description": "Web components for ixfx — Lit-based UI toolkit",
   "author": "Clint Heyer",