Tatu Lund

State of this is a bit confusing, as it is already included in the documentation, but looks like not implemented yet https://vaadin.com/docs/latest/fusion/advanced/custom-serialization

This could be fixed by https://github.com/vaadin/framework/pull/11988

Thank you for the contribution. In the pom.xml line 53 seems to be code formatting issue, perhaps you used tabs instead of spaces.

@chrisnaan Thanks for quick action. I am curious to know, are you using OSGi with Liferay or Karaf ?

Could you test if adding `@Uses(TextField.class)` annotation in your class solves the problem. I think your problem is that because there is no actual TextField class reference in your class,...

It is documented in API https://vaadin.com/api/platform/23.0.1/com/vaadin/flow/component/dependency/Uses.html But it could be good to have reference to this somewhere in vaadin.com/docs. Your input would be valuably to define in which context it...

True. Same holds for as required indicator. When field is used with Binder, one should not directly control these, but let Binder take care of it.

Currently documentation states the following (which covers also this use case, but not explicitly) https://vaadin.com/docs/v8/framework/datamodel/datamodel-forms.html The validation state of each field is updated whenever the user modifies the value of...

This issue should not happen with Vaadin 8 anymore as similar bug was fixed by https://github.com/vaadin/framework/pull/11436 However this may be still a problem with Vaadin 7.

This happens with other layout components too, e.g. VerticalLayout. And it looks like it is weird timing issue. I briefly checked SliderConnector and VSlider code and could not figure out...