Vaadin Flow 8.0.5
Changes in Flow from 8.0.4
-
Breaking Changes:
-
⧉ Prevent deadlock in findOrCreateVaadinSession (#11520) (CP: 8.0). PR:12323. Ticket:12316
It is possible findOrCreateVaadinSession leaves session locked if HTTP session is invalidated in an another thread between lockSession and unlockSession calls. This PR changes the implementation so that this can no longer happen. BREAKING CHANGE: VaadinService::lockSession now must return the lock, and VaadinService::unlockSession must accept it as a parameter. If you have overridden these methods, you must adapt your implementation accordingly. Cherry pick of #11520
-
-
Fixes:
-
⧉ Update minimum supported browser versions (#12391). PR:12395
-
⧉ Make webpack work with Node 17.1+ (#12353). PR:12371. Tickets: 12246, 12285
Disallows usage of Node 17.0.
-
⧉ Avoid processing value change event due writing back of converted value (#12183) (CP: 8.0). PR:12340
-
⧉ Ensure that side effects of readBean do not set hasChanges true (#12181). PR:12319
JavaDoc of hasChanges says: "Check whether any of the bound fields' have uncommitted changes since last explicit call to readBean(Object), removeBean(), writeBean(Object)} or writeBeanIfValid(Object)." If readBean has converters, they will be run and field values updated accordingly. Furthermore if fields have value change listenersthat will produce further changes in values, this should be considered according to above as part of readBean procedure and thus hasChanges still should return false. Cherry pick from: vaadin/framework#12455 (cherry picked from commit 4e36fd9)
-