Menu Button

<%# Markup for the menu (APG Menu Button) demo.
    stimeo--menu is a full role="menu"/"menuitem" menu providing arrow-key roving
    focus, Esc, and outside click (distinct from the disclosure dropdown).
    Positioning (static placement) is the Playground's CSS. %>
<div class="menu" data-controller="stimeo--menu">
  <button
    id="menu-trigger"
    type="button"
    class="demo-trigger"
    aria-haspopup="menu"
    aria-expanded="false"
    aria-controls="menu-list"
    data-stimeo--menu-target="trigger"
    data-action="click->stimeo--menu#toggle keydown->stimeo--menu#onTriggerKeydown">
    <%= t("components.menu.demo.trigger") %>
  </button>

  <%# The trigger labels the menu; each item is a role="menuitem" button (tabindex=-1).
      Items need no data-action: the controller handles their clicks and keys from its own
      element, so items added or moved in later work without being wired up. %>
  <ul id="menu-list" class="menu__list" role="menu" aria-labelledby="menu-trigger"
      data-stimeo--menu-target="menu" hidden>
    <li role="none">
      <button type="button" role="menuitem" class="demo-menuitem" tabindex="-1"
              data-stimeo--menu-target="item"><%= t("components.menu.demo.edit") %></button>
    </li>
    <li role="none">
      <button type="button" role="menuitem" class="demo-menuitem" tabindex="-1"
              data-stimeo--menu-target="item"><%= t("components.menu.demo.duplicate") %></button>
    </li>
    <li role="none">
      <button type="button" role="menuitem" class="demo-menuitem" tabindex="-1"
              data-stimeo--menu-target="item"><%= t("components.menu.demo.delete") %></button>
    </li>
  </ul>
</div>

<%# Readout: what the component just reported. Purely visual — the component
    already announces what a screen reader needs, so this line is aria-hidden to
    keep it from being read twice. The value is a code fragment (API identifiers
    and values), so only the label is translated. %>
<p class="demo-readout" aria-hidden="true">
  <span><%= t("catalog.readout.events") %></span>
  <span class="demo-readout__value" data-readout>—</span>
</p>

/*
 * Presentation-only styles for the menu (Menu Button) demo.
 * This demo uses static CSS placement below the trigger. Consumers that need
 * viewport-aware collision handling can compose the menu with the opt-in
 * stimeo-ui/positioning entrypoint.
 */

.menu {
  position: relative;
  display: inline-block;
}

.menu__list {
  position: absolute;
  left: 0;
  margin: 0.25rem 0 0;
  padding: 0.25rem;
  list-style: none;
  min-width: 12rem;
  background: var(--surface-card);
  border: 1px solid var(--border-strong);
  border-radius: 0.375rem;
  box-shadow: 0 8px 24px rgba(0, 0, 0, 0.12);
}

// Every move of the open state is reported, with a `reason` saying what drove it
// — a trigger, Escape, a click outside, or a call from your own code. A real app
// subscribes to mirror the state elsewhere or to send an analytics event; this
// demo writes the event name and its reason into the readout so both are visible
// while you interact. `reason: "api"` is the one to watch for: a close you asked
// for comes back to your own listener.
// The page chrome uses some of these controllers too (the nav, the tab strip),
// so everything below is scoped to the demo itself.
const demoStage = document.querySelector(".demo-stage") ?? document;
const stateReadout = demoStage.querySelector("[data-readout]");
const stateRoot = demoStage.querySelector("[data-controller~='stimeo--menu']");

for (const name of ["open", "close"]) {
  stateRoot?.addEventListener(`stimeo--menu:${name}`, (event) => {
    const reason = event.detail?.reason;
    if (stateReadout) {
      stateReadout.textContent = reason
        ? `stimeo--menu:${name} · reason: ${reason}`
        : `stimeo--menu:${name}`;
    }
  });
}