v3.34.3

Fixes

• Dropdown: a non-button trigger works again (#77). A dropdown with no explicit trigger used the first <button> it found, and that search included the menu. With a link or other non-button trigger (e.g. <atom:link>), the first menu item became the trigger: the link didn't open the menu, and clicking that item didn't close it. The trigger lookup now skips anything inside the menu, in this order: an element with data-atom-dropdown-trigger, then the first <button>, then the first child element.
• Dropdown: a control inside the menu no longer becomes the outer menu's trigger. Date-pickers and email/colour inputs mark their own trigger with data-atom-dropdown-trigger. Placed inside another dropdown's menu, that marker used to become the outer dropdown's trigger. It is now ignored.
• Table filters: "More filters" stays open while you use a filter inside it (#80). The menu closed on any click inside it, so a date-picker, date-range or variant="filter" select placed there couldn't be used.

Behaviour change

The "More filters" menu of <atom:table.filters> is now locked. It closes on Esc or a click outside, not when something inside it is clicked. If your app puts its own buttons or links in the more slot and relied on the menu closing on click, close it yourself.

Docs

The dropdown docs explain how the trigger is chosen and add demos for a link trigger and for data-atom-dropdown-trigger.

dist/ is rebuilt. No consumer CSS rebuild is needed.