Conversation
|
Warning: this PR brings in an incompatible change since it changes the result type of
|
mcollovati
left a comment
There was a problem hiding this comment.
Overall LGTM, but I have a couple of questions:
- do we still need to use the property descriptor in the
Inputelement? - shouldn't also
RangeInputimplement the new interface? - should we also update the
InputTextElementinflow-html-components-testbenchto make it implementcom.vaadin.testbench.HasPlaceholder
|
BTW, we should probably create an issue for implementing the testbench |
Unfortunately yes, because Input element sets the placeholder attribute, while all other web components and all
Nope,
Yup, but I can't figure out how to run IT tests in flow-html-components-testbench unfortunately.
Agree: #18093 |
|
Kudos, SonarCloud Quality Gate passed!
|
|
This ticket/PR has been released with Vaadin 24.3.0.alpha6 and is also targeting the upcoming stable 24.3.0 version. |








Description
Implement the HasPlaceholder interface.
Fixes #4068
Type of change
Checklist
Additional for
Featuretype of change