Skip to content
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

TextArea: Allow value null to prevent standard libarary to throw errors #6475

Closed
1 of 4 tasks
C3ntraX opened this issue Feb 13, 2023 · 2 comments · Fixed by #6493
Closed
1 of 4 tasks

TextArea: Allow value null to prevent standard libarary to throw errors #6475

C3ntraX opened this issue Feb 13, 2023 · 2 comments · Fixed by #6493

Comments

@C3ntraX
Copy link

C3ntraX commented Feb 13, 2023

Feature Request Description

See #6472

Standard libarary throwing errors because the textarea value does not accept null.

Proposed Solution

A clear and concise description of the solution you would like to have.

Proposed Alternatives

A clear and concise description of any alternative solutions or features you've considered.

Additional Context

Add other context or screenshots related to the feature request here.

Priority

  • Low
  • Medium
  • High
  • Very High

A clear and concise description of the impact/urgency of the required feature.

Stakeholder Info (if applicable)

  • Organization: {...}
  • Business impact: {...}
@C3ntraX
Copy link
Author

C3ntraX commented Feb 13, 2023

The input value does accept null although the api states otherwise, but its was not noticed because the input does not throw an error.
https://sap.github.io/ui5-webcomponents/main/playground/components/Input/

Therefore it makes sense to update the api for the Input Element as well.

@s-todorova
Copy link
Contributor

Hello @SAP/ui5-webcomponents-topic-rl,

This feature request is related to #6472. Could you please check the referenced issue and analyze whether it is espected to be able to set the ui5-textarea value to "null" ?

Kind regards,
Siyana

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

3 participants