-
Bug
-
Resolution: Fixed
-
Neutral
-
5.6
-
None
-
None
-
-
Empty show more show less
-
Basel 119
-
2
Crop tool is always disabled after migration to Vaadin 8.
After quick investigation it turned out that enable-state checks on the client-side yield incorrect values because enabled property is no longer present on the client-side.
My guess is that it happens cause true is the default value of the enabled-state and Vaadin does not communicate that to the client-side at all! Sounds like a not correct behaviour by Vaadin (cause on the client-side the property ends up to be undefined!)
The fix anyway would be to introduce a dedicated function in the crop tool connector that'd check if enabled property is explicitly set to false.
Acceptance criteria