-
Notifications
You must be signed in to change notification settings - Fork 83
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
fix: apply initially set custom field value to inputs #7882
Conversation
4726554
to
45877cb
Compare
f011ee0
to
b88a143
Compare
Quality Gate passedIssues Measures |
Hi @web-padawan and @web-padawan, when i performed cherry-pick to this commit to 24.4, i have encountered the following issue. Can you take a look and pick it manually? |
Co-authored-by: Serhii Kulykov <[email protected]>
Description
Fixes #7871
Added logic to store the
value
property set initially and apply it to inputs after they are populated.Also added integration tests to cover the case when inputs are not yet upgraded (only happens for Vaadin web components but works with native
<input>
elements, see the issue description).Type of change