mui / mui/material-ui

Autocomplete don't get disabled value from FormControl

Open
#34,418 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs scope: autocomplete
Dominant language
JavaScript
Stars
99.1k
Forks
32.5k
Avg merge
2d 17h
Merged PRs (30d)
106

Description

Duplicates
  • I have searched the existing issues
Latest version
  • I have tested the latest version
Steps to reproduce 🕹

Hello,

I'm trying to customize the Autocomplete component.

I want to use it with a FormControl as I use it with my other custom components.
The FormControl should control the "disabled" and "error" state of the input.

But, with the Autocomplete, the disable prop is not passed to the Autocomplete renderInput.

Here is an example : https://codesandbox.io/s/brave-bird-kv5jcc?file=/demo.tsx

As you can see in the console, the disable prop is equal to false, but true in the FormControl.

Current behavior 😯

With the Autocomplete, the disable prop is not passed to the Autocomplete renderInput.

Expected behavior 🤔

The FormControl should control the "disabled" state of the input.

Context 🔦

I want to customize the Autocomplete.
I already customized input

Your environment 🌎
npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked CodeSandbox reproduction and inspect how Autocomplete uses renderInput with a FormControl. Compare the disabled value reported by FormControl with the prop received by the Autocomplete input. Done means the FormControl-controlled disabled state reaches the customized input and the reproduction no longer shows conflicting values.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.