-
Notifications
You must be signed in to change notification settings - Fork 273
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
[Select]: Set default value no work #10537
Comments
Hi @pupss89345 I wasn't able to reproduce this: https://stackblitz.com/edit/github-vdvctzza?file=src%2FApp.tsx Please see the linked StackBlitz example and let me know if I missed something. |
Hmm, this is strange. I've updated the example to use only 2.5.0 of both ui5-webcomponents and ui5-webcomponents-react packages and the behavior is still the same: https://stackblitz.com/edit/github-vdvctzza-dtwarrta?file=src%2FApp.tsx Could you check which version of
|
Maybe I found the issue. It could be due to the way I created the React project and the UI5 components causing a conflict. I created the project using:
Then I added: And then Select component set Value don't work.
|
I've tested the behavior and can confirm that it occurs when using Since the Hi Colleagues, when using create-react-app (not maintained anymore) to set up a React application, the I've created an example which you can check out by forking this repo. Reproduction steps
|
Describe the bug
As title said the Select component set value is no work,,,,
<Select value="Orange" valueState="None" > <Option>Apple</Option> <Option>Orange</Option> </Select>
I set value is Orange but always apple as default value
Isolated Example
No response
Reproduction steps
1.Set Select Value as Orange
2.show wrong result
3.
...
Expected Behaviour
No response
Screenshots or Videos
No response
UI5 Web Components for React Version
2.5.0
UI5 Web Components Version
2.5.0
Browser
Edge
Operating System
Win11
Additional Context
No response
Relevant log output
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: