question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Joy][Select] not render a input element

See original GitHub issue

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Steps to reproduce 🕹

Steps:

Current behavior 😯

Joy Select not render input element.

Expected behavior 🤔

It should render a <input aria-hidden tabIndex="-1"/> just like Material UI Select .

Context 🔦

No response

Your environment 🌎

npx @mui/envinfo
  npmPackages:
    @emotion/react: ^11.10.4 => 11.10.4
    @emotion/styled: ^11.10.4 => 11.10.4
    @mui/base:  5.0.0-alpha.92
    @mui/core-downloads-tracker:  5.10.6
    @mui/icons-material: latest => 5.8.4
    @mui/joy: * => 5.0.0-alpha.47
    @mui/material:  5.9.3
    @mui/private-theming:  5.10.6
    @mui/styled-engine:  5.10.6
    @mui/system:  5.10.6
    @mui/types:  7.2.0
    @mui/utils:  5.10.6
    @types/react: ^17.0.47 => 17.0.48
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript: ^4.7.4 => 4.7.4

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
siriwatknpcommented, Oct 7, 2022

Is this issue still up for grabs? I would like to work on this.

Go ahead!

0reactions
michaldudakcommented, Oct 20, 2022

The useSelect hint could hint that the input should be rendered by providing a getHiddenInputProps

Good idea!

Also, there is no harm in adding the hidden input always (even when name is not specified) so it should be fine even if in userland the logic for it is not added.

Sure, we can do it. I wanted to keep the rendered DOM cleaner in case there’s no need for an input, but on the other hand, this behavior could be surprising for developers. I don’t really have a strong opinion on this one, so if you think having the input all the time is better, I’m happy to implement it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

mui/material-ui - [Joy][Select] not render a input element - GitHub
Joy Select not render input element. Expected behavior. It should render a <input aria-hidden tabIndex="-1"/> just like Material ...
Read more >
React - Pseudo element on Input not rendered at all [duplicate]
I am trying to make a performance friendly focus effect on an input element, so when it's in focus, it gets a nice...
Read more >
How to use Material UI Select in React - Refine Dev
The code above showcases a Material UI Select input field with popular car brands as the option values. Here's the result: MUI select...
Read more >
<input type="url"> - HTML: HyperText Markup Language | MDN
The <input> element's value attribute contains a string which is automatically validated as conforming to URL syntax.
Read more >
Refs and the DOM - React
Refs provide a way to access DOM nodes or React elements created in the render method. In the typical React dataflow, props are...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found