[Migration] Unable to find the input element. It was resolved to [object HTMLDivElement] while an HTMLInputElement was expected.
See original GitHub issue- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
I am getting this error:
index.js:1 MUI: Unable to find the input element. It was resolved to [object HTMLDivElement] while an HTMLInputElement was expected.
Instead, Autocomplete expects an input element.
Make sure you have customized the input component correctly.
When I use autocomplete like this:
<Autocomplete
freeSolo
autoHighlight
style={{ width: 350 }}
open={open}
onOpen={() => setOpen(true)}
onClose={() => setOpen(false)}
onChange={(_event, user) =>
router.push(`/projects/${project.id}/users/${user.id}`)
}
onInputChange={(_event, newValue) => setValue(newValue)}
isOptionEqualToValue={(option, optionTwo) => option.id === optionTwo.id}
getOptionLabel={(user) => presentUser(user, project)}
groupBy={(user) => capitalizeFirstLetter(user.userType)}
options={options}
loading={loading}
renderInput={(params) => (
<div ref={params.InputProps.ref}>
<Input
{...params.inputProps}
variant="filled"
className={classes.searchInput}
classes={{ underline: classes.searchInputUnderline }}
placeholder="Search"
startAdornment={
<InputAdornment position="start">
<Search />
</InputAdornment>
}
endAdornment={
<>
{loading ? (
<CircularProgress color="inherit" size={20} />
) : null}
{params.InputProps.endAdornment}
</>
}
type="text"
/>
</div>
)}
/>
It worked with v4. According to the documentation it seems like I am doing it correctly.
Expected Behavior 🤔
No errors should happen.
Context 🔦
Simply trying to upgrade to v5
Your Environment 🌎
Chrome.
`npx @mui/envinfo`
System:
OS: macOS 11.3.1
Binaries:
Node: 14.17.1 - ~/.nvm/versions/node/v14.17.1/bin/node
Yarn: 1.22.11 - /opt/homebrew/bin/yarn
npm: 7.23.0 - /opt/homebrew/bin/npm
Browsers:
Chrome: 93.0.4577.82
Edge: Not Found
Firefox: Not Found
Safari: 14.1
npmPackages:
@emotion/react: ^11.4.1 => 11.4.1
@emotion/styled: ^11.3.0 => 11.3.0
@mui/core: 5.0.0-alpha.49
@mui/icons-material: ^5.0.1 => 5.0.1
@mui/lab: ^5.0.0-alpha.49 => 5.0.0-alpha.49
@mui/material: ^5.0.2 => 5.0.2
@mui/private-theming: 5.0.1
@mui/styled-engine: 5.0.1
@mui/styles: ^5.0.1 => 5.0.1
@mui/system: 5.0.2
@mui/types: 7.0.0
@mui/utils: 5.0.1
@mui/x-data-grid: ^4.0.0 => 4.0.0
@types/react: 17.0.22
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
[Migration] Unable to find the input element. It was resolved to ...
I am getting this error: index.js:1 MUI: Unable to find the input element. It was resolved to [object HTMLDivElement] while an HTMLInputElement ...
Read more >Angular 8 ERROR Error: Unable to find context associated ...
That said, the following error "Unable to find context associated with [object HTMLDivElement]" returns from Chrome DevTools after npm run ...
Read more >Useful Patterns by Use Case - React TypeScript Cheatsheets
Wrapping/Mirroring a HTML Element. Usecase: you want to make a <Button> that takes all the normal props of <button> and does extra stuff ......
Read more >HTML Standard
1 Introduction; 2 Common infrastructure; 3 Semantics, structure, and APIs of HTML documents; 4 The elements of HTML; 5 Microdata; 6 User interaction ......
Read more >TypeScript support in Svelte - Learn web development
In this article we took our to-do list application and ported it to TypeScript.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So I managed to find the issue. This line:
Had to be changed to:
Since I was using which itself is not directly an , but rather a div with an input inside
I had this issue, solved by adding {…params.inputProps} to the input in the
renderInput
props as per https://mui.com/material-ui/react-autocomplete/#combo-boxPlease note that it is
inputProps
NOTInputProps
, hope it helps.