-
Notifications
You must be signed in to change notification settings - Fork 4.1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Support for no client-side javascript #1178
Comments
+1 would be an awesome feature saving tons of hackery currently needed. Perhaps "degraded": "select" might be a nicer config? |
@goofballLogic I've forked my initial suggestion into this version: https://github.com/gareth-robinson/react-select/tree/allowNoClient |
@JedWatson is there anything I can do to facilitate this feature request? Happy to review / help edit. |
+1 I am also waiting for this to be fixed |
Hello - In an effort to sustain the We understand this might be inconvenient but in the best interest of supporting the broader community we have to direct our limited efforts to maintain the latest version. If you feel this issue / pull request is still relevant and you'd like us to review it, please leave a comment and we'll do our best to get back to you. |
I did offer to contribute/help. some of us still care about isomorphism... |
Thank you for your reply @goofballLogic, we'll re-open this! |
In an attempt to give more transparency to issues, I will be transferring this as well as other non-critical feature requests to the Discussions area where they can be voted on and discussed more in depth. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi there, we're using react-select in a project, but would like the option of degrading gracefully (or progressively enhancing, depending on your point of view) so that we still have a working select when there is no client-side javascript. Currently react-select just renders an unstyled and untyped input field in this case.
The aim would be that with some additional prop (e.g. allowNoClient) the select would render the currently hidden input as a and the componentDidMount method would set an additional state entry (e.g. hasClient). The render method would check both these values to determine how to render the input field. Use of this option may then only support a subset of the react-select functionality i.e. simple string options only, no async loading, but a developer would choose which was most important to them.
The text was updated successfully, but these errors were encountered: