@rcarls/rc-adaptive-menu 0.0.0-next-20260921045401

package/CHANGELOG.md

@@ -0,0 +1,45 @@
+# @rcarls/rc-adaptive-menu
+
+## 0.0.0-next-20260921045401
+
+### Patch Changes
+
+- Updated dependencies [50d5610]
+- Updated dependencies [4341311]
+  - @rcarls/rc-common@0.0.0-next-20260921045401
+
+## 0.6.0
+
+### Minor Changes
+
+- 7382c71: Add a priority-aware action toolbar that moves original controls into an
+  overflow menu. Which actions are promoted is a purely declarative computation
+  from `max-shown` and each action's `data-priority`/authored `slot`, with no
+  runtime measurement of the toolbar's or its children's rendered size: a
+  consumer whose promoted count needs to react to available space owns that
+  decision and writes the resulting `max-shown` value down. Include controlled
+  and uncontrolled open state, keyboard navigation, light dismissal, and a
+  non-Popover fallback.
+
+  Fix `--rc-adaptive-menu-touch-target-overlap-inline-start`/`-end`: the host's
+  own `max-inline-size: 100%` self-referenced a shrink-to-fit ancestor's
+  already-margin-reduced auto size (an app bar's own trailing group, for
+  example), quietly clamping the host back down and canceling the overlap out
+  from under it. The cap now grows by the overlap amount so it only ever bounds
+  the host's real content.
+
+- 7382c71: Add `--rc-adaptive-menu-touch-target-overlap-inline-start` and
+  `-inline-end`, zero by default. A theme or consumer sets one to let the
+  overflow trigger's accessible touch-target inflation on that side overlap
+  into whatever sits just outside the host, such as a toolbar's own edge
+  padding, instead of also reserving layout space there (the overflow
+  trigger is conventionally the trailing-most control in a toolbar, so
+  `-inline-end` is the one commonly set). Mirrors `@rcarls/rc-button`'s and
+  `@rcarls/rc-menu-button`'s own touch-target overlap tokens.
+
+### Patch Changes
+
+- Updated dependencies [6683eb9]
+- Updated dependencies [ee7ba6c]
+- Updated dependencies [30eb232]
+  - @rcarls/rc-common@0.6.0

package/README.md

@@ -0,0 +1,74 @@
+# `@rcarls/rc-adaptive-menu`
+
+Priority-aware action toolbar that preserves authored controls while moving
+lower-priority actions into an overflow menu. The same light-DOM nodes remain
+connected, so framework handlers, form behavior, dialog invokers, and element
+references keep working when an action moves.
+
+Docs: [https://richardcarls.github.io/rc-webcomponents/components/rc-adaptive-menu](https://richardcarls.github.io/rc-webcomponents/components/rc-adaptive-menu).
+
+## Installation
+
+```bash
+npm install @rcarls/rc-adaptive-menu
+```
+
+## Usage
+
+```html
+<rc-adaptive-menu label="Document actions" max-shown="3">
+  <button type="button" data-priority="30">
+    <span data-rc-menu-leading aria-hidden="true">★</span>
+    <span data-rc-menu-label>Favorite</span>
+  </button>
+  <button type="button" data-priority="20">
+    <span data-rc-menu-leading aria-hidden="true">✎</span>
+    <span data-rc-menu-label>Edit</span>
+  </button>
+  <button type="button" slot="overflow">
+    <span data-rc-menu-label>Delete</span>
+  </button>
+</rc-adaptive-menu>
+
+<script type="module">
+  import '@rcarls/rc-adaptive-menu/define';
+</script>
+```
+
+Larger numeric `data-priority` values are promoted first, with DOM order as the
+tie breaker, up to `max-shown` authored actions. Author `slot="overflow"` to
+keep an action in the overflow menu regardless of `max-shown`. A negative
+`data-priority` has the same effect: the action always overflows. The overflow
+menu renders in authored DOM order (native slot distribution isn't
+JS-ordered), so author negative-priority actions after normal-priority ones to
+have them appear last. `max-shown` is a static declarative cap, re-evaluated
+whenever it or an authored action's `data-priority` changes: the component
+does not measure its own or its children's rendered size, so promoted actions
+are not guaranteed to visually fit any particular container. A consumer that
+needs the promoted count to react to available space (a breakpoint, a
+container query, a window size class) owns that decision and writes the
+resulting `max-shown` value down. When the authored set changes, the
+component changes the actions' slot, `role`, and `tabindex`, then restores
+the authored values when they return or disconnect. Demoted `rc-menu-button`
+actions also receive vertical menu-row orientation while overflowed, with
+their authored orientation restored when promoted or disconnected.
+
+In horizontal mode the toolbar is a plain shrink-to-fit flex row:
+`max-inline-size: 100%` keeps it constrained by its allocated space, but its
+own preferred width is ordinary CSS, sized to only the actions actually
+promoted. No JS-computed intrinsic-size hint is involved.
+
+Use `data-rc-menu-leading`, `data-rc-menu-label`,
+`data-rc-menu-trailing`, and `data-rc-menu-shortcut` to expose menu content
+regions to themes shared with `rc-menu`.
+
+The visible overflow button and its activation area can be sized independently
+with `--rc-adaptive-menu-trigger-*` and
+`--rc-adaptive-menu-touch-target-*`. The default activation-area floor is
+`3rem` in both axes.
+
+Use `default-open` for initial uncontrolled state, or write `open` and handle
+`rc-adaptive-menu-toggle` for controlled state. The event reports the state
+requested by user interaction; property writes and `openMenu()`, `closeMenu()`,
+and `toggleMenu()` calls are silent. The `$actions`, `$promotedActions`, and
+`$overflowedActions` getters expose the original nodes in current DOM order.