Dropdown Menu

Preview

Items are set in a script: el.items = [{ label: "Edit", action: "edit" }, …].

<esa-dropdown-menu id="dd-start" position="below-start">
  <button>Actions ▾</button>
</esa-dropdown-menu>

import { Component, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';
import '@esa/ecology/esa-dropdown-menu';

@Component({
  selector: 'app-dropdown-menu-demo',
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <esa-dropdown-menu id="dd-start" position="below-start">
      <button>Actions ▾</button>
    </esa-dropdown-menu>
  `,
})
export class DropdownMenuDemo {}

Positions

<esa-dropdown-menu position="below-start">…</esa-dropdown-menu>
<esa-dropdown-menu position="below-end">…</esa-dropdown-menu>

import { Component, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';
import '@esa/ecology/esa-dropdown-menu';

@Component({
  selector: 'app-dropdown-menu-demo',
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <esa-dropdown-menu position="below-start">…</esa-dropdown-menu>
    <esa-dropdown-menu position="below-end">…</esa-dropdown-menu>
  `,
})
export class DropdownMenuDemo {}

API

Methods

Events

Accessibility

• The panel is role="menu" and each item is role="menuitem"; dividers are role="separator".
• Disabled items set the native disabled attribute and are skipped on activation.
• Escape and any outside click close the menu.

Theming surface

Every public token this component reads, extracted from its source at build time, split by blast radius: the hooks that belong to this component, then the shared and system tokens it consumes alongside everything else. The Resolves to column walks each token's real lineage — component → semantic → primitive → raw value — so you can see exactly where re-pointing it lands. A spoke re-skins by overriding these in its theme-<slug>.css; component internals are never edited. No hook for what you need? File it with /request-lego.

Type roles it names

This component does not set a size, weight, face or tracking of its own — it names a composite, and the composite carries all five. A composite is a class rather than a token, so none of it appears in the tables below; re-theme text by re-pointing the token family, not by editing the component.

Wired to this component

No other component reads these — re-point them and esa-dropdown-menu is the only thing that moves.

Shared tokens it reads

Owned by a family or by the semantic layer. Still overridable — but scope the override (esa-foo { --form-border-color: … }) unless you mean to move everything that reads it. Reach says what else that is.