Skip to content

[combobox] Popup closes automatically when list is filtered in multiple #3181

Closed

Description

@mirka

Bug report

Current behavior

In the multiple case, the popup stays open when items are toggled. However, the popup will close after each item toggle if the list happens to be filtered.

Expected behavior

I think it's generally better for the popup to stay open regardless of whether the list is filtered.

Reproducible example

As seen in the official example:

CleanShot.2025-11-11.at.02-22-56.mp4

Base UI version

1.0.0-beta.4

Which browser are you using?

Chrome

Which OS are you using?

Mac OS

Activity

  1. mj12albert commented on Nov 11, 2025

    @mj12albert
    Member
  2. added
    type: bugIt doesn't behave as expected.
    and removed on Nov 11, 2025
  3. atomiks commented on Nov 11, 2025

    @atomiks
    Contributor

    This was "intentional" since when you've filtered the list, clearing the input after selection would cause all the items to show again which might be disorienting for the user due to layout shift. I am open to changing the behavior, though

  4. mj12albert commented on Nov 11, 2025

    @mj12albert
    Member

    clearing the input after selection would cause all the items to show again

    Could it retain the input value after selection? I may want to make multiple selections based on one "input filter", e.g. type "Star Wars" and pick multiple movies

  5. atomiks commented on Nov 11, 2025

    @atomiks
    Contributor

    @mj12albert I think that UX flow is worse as a default but it could be useful..

    FWIW our behavior matches Material UI Autocomplete, though theirs closes even when not filtering

  6. mirka commented on Nov 11, 2025

    @mirka
    ContributorAuthor

    Ok yeah I see that. Keeping the input value after selection is great when wanting to select multiple Star Wars movies, but slower when you want to select multiple unrelated movies. There may be cases where you can know beforehand what the more common interaction is, but not always.

    I also find it more palatable to keep the input value after selection when the input is placed inside the popup, completely separate from the chips. It's a lot more awkward to do so when the input is placed alongside the chips, because the illusion is that the input value "morphs" into a chip when an item is selected.

  7. added
    type: expected behaviorThe current behavior is already the one expected.
    and removed
    type: bugIt doesn't behave as expected.
    on Nov 11, 2025
  8. mj12albert commented on Nov 11, 2025

    @mj12albert
    Member

    Yeah it seems pretty contextual based on the use-case/dataset. It seems quite easy to not auto-close and keep the input value by using onOpenChange: https://stackblitz.com/edit/bcocshwo-kkp2dff4?file=src%2FApp.tsx

    It wouldn't be as easy doing it the other way round

  9. added
    has workaroundThere’s a bug, but users have a complete workaround, so no urgent fix or release is needed.
    on Feb 9, 2026
  10. atomiks commented on Oct 20, 2026

    @atomiks
    Contributor

    Closing as answered: keeping the popup open and preserving the filter after selection is now documented. The related cancellation fixes shipped in v1.8.0 through #5362. Which request to cancel depends on the input’s placement; the filter still resets when the popup closes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component: comboboxChanges related to the combobox component.has workaroundThere’s a bug, but users have a complete workaround, so no urgent fix or release is needed.type: expected behaviorThe current behavior is already the one expected.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions