[Autocomplete] freesolo forces an autocomplete entry on enter

[arishoham]

Screen.Recording.2025-08-12.at.12.54.11.PM.mov

Steps to reproduce

Steps:

1. Open this link to live example: https://stackblitz.com/edit/github-cfngmona-azw9frdq?file=src%2FApp.tsx
2. type in "pe"
3. press enter, "pediatric ent" is selected

Current behavior

Steps:

1. Open this link to live example: https://stackblitz.com/edit/github-cfngmona-azw9frdq?file=src%2FApp.tsx
2. type in "pe"
3. press enter, "pediatric ent" is selected

Screen.Recording.2025-08-12.at.12.54.11.PM.mov

Expected behavior

Steps:

1. Open this link to live example: https://stackblitz.com/edit/github-cfngmona-azw9frdq?file=src%2FApp.tsx
2. type in "pe"
3. press enter, "pe" should be in input, and the onInputChange should register with "pe"

Context

Issue was introduced with #46489

Your environment

npx @mui/envinfo

browser: chrome 138.0.7204.184

System:
    OS: macOS 15.6
  Binaries:
    Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
    npm: 11.2.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 139.0.7258.67
    Edge: Not Found
    Safari: 18.6
  npmPackages:
    @base-ui-components/react:  1.0.0-beta.2 
    @base-ui-components/utils:  0.1.0 
    @emotion/react:  11.14.0 
    @emotion/styled:  11.14.1 
    @mui/core-downloads-tracker:  7.3.1 
    @mui/icons-material:  7.3.1 
    @mui/lab:  7.0.0-beta.16 
    @mui/material:  7.3.1 
    @mui/material-nextjs:  7.3.0 
    @mui/private-theming:  7.3.1 
    @mui/styled-engine:  7.3.1 
    @mui/system:  7.3.1 
    @mui/types:  7.4.5 
    @mui/utils:  7.3.1 
    @mui/x-charts:  8.10.0 
    @mui/x-charts-vendor:  8.6.0 
    @mui/x-date-pickers:  8.10.0 
    @mui/x-internal-gestures:  0.2.3 
    @mui/x-internals:  8.10.0 
    @types/react:  18.3.13 
    react:  18.3.1 
    react-dom:  18.3.1 
    typescript: 5.9.2 => 5.9.2

Search keywords: freesolo, autocomplete

[mj12albert]

Looks very similar to #46718

Does it occur in your case without freeSolo? @arishoham

[ZeeshanTamboli]

Using freeSolo together with autoHighlight doesn’t really make sense. If the intent is to allow arbitrary input (freeSolo), then automatically highlighting the first matching option contradicts that behavior. Also, can you clarify how this relates to #46489?

[github-actions]

Since the issue is missing key information and has been inactive for 7 days, it has been automatically closed. If you wish to see the issue reopened, please provide the missing information.