-
Notifications
You must be signed in to change notification settings - Fork 82
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
Expose slotted input feature on field components #84
Comments
Also related to https://github.com/vaadin/vaadin-login/issues/96 since this effectively prevents you from placing Vaadin components into the Login component as custom content, since the username/password autocompletion will be disabled. |
Another related issue is https://github.com/vaadin/vaadin-core/issues/238 (field wrapper component). |
In our case, slotted input feature is highly useful to integrate with existing GUI form-building backend mini-apps, for visual upgrade. Advanced and very expensive to reimplement JS-based features like conditional logic, multi-page etc can stay compatible with much less work - if they have input available for processing in light DOM. |
Prototype which we can use for inspiration: https://vaadin-form-prototype.glitch.me |
@web-padawan Impressive work! Looks really promising! |
Thanks! The prototype is actually created by @jouni |
Closing as shipped in Vaadin 22 stable release that landed today. |
Because of Shadow DOM limitations, our components such as
vaadin-text-field
do not work well with autocomplete and some password managers because the<input>
element is not in the light DOM by default.We have undocumented slotted
<input>
feature invaadin-text-field
but not in other components.At the same time we have the following components that support providing a custom input in a different way.
vaadin-combo-box-light
vaadin-date-picker-light
Let's discuss if we should implement slotted
<input>
support in all the components for consistency.Related issues:
The text was updated successfully, but these errors were encountered: