v133 · dom

Popover nested inside invoker shouldn't re-invoke it

In this case:

concepts

  1. Nested popover invoker

    A popover trigger nested inside the popover it opens no longer re-invokes (and closes) the popover. Removes a class of UI flicker bugs.

  2. Before / after comparison

    Two identical nested-invoker scenarios side-by-side, one in legacy mode and one in 133 mode — the flicker the fix eliminates.

  3. Live toggle event log

    Click a nested invoker and watch the beforetoggle / toggle events. Just one open event — no more open / close / open thrash.

  4. Action menu inside popover

    A File/Edit toolbar with a "Share" sub-menu nested inside the File dropdown. Click Share — the sub-panel opens without closing or flickering the parent dropdown. The real-world pattern the Chrome 133 fix enables.

why it shipped

The current behavior is odd - clicking on an open popover doesn't close that popover in any other circumstance. The change makes that assumption correct, even in this weird corner case.

references