Vaadin Flow 2.11.2
Changes since 2.11.1
Fixes
-
Clear CurrentInstance before invoking new session tasks (#6349) (#20255)
Commit · Pull request · IssueCommands enqueued by VaadinSession.access() in general have nothing to do with each other. The only thing they have in common is they share the same VaadinSession (and, by implication, VaadinService). Therefore, if command №1 invoked UI.setCurrent() and command №2 invokes UI.getCurrent(), command №2 should read null, not the random UI from command №1 that it has nothing to do with.