-
Notifications
You must be signed in to change notification settings - Fork 183
Description
Description of the bug
-
The v24 documentation for @ClientCallable only mentions Polymer, making the reader doubt that it applies to LitElement.
When in fact, elsewhere it is mentioned that ClientCallable is the correct way to call back instead of propagating events. -
The documentation to @ClientCallable MUST explain when @AllowInert is be needed. I just lost 2 days trying to figure out why something worked in v14 and v23 but not in v24:
- even though the need for AllowInert is said to have been introduced in v23, my code ported from v14 to v23 worked fine without @AllowInert
- but in v24, if a page starts a modal dialog but has a running web component (for example a timer) in the background, then @clientcallable calls don't work.
Expected behavior
N/A, documentation
Or maybe make AllowInert the default, as it is completely counter-intuitive.
Minimal reproducible example
N/A
Versions
Vaadin: 24.1.4
Flow: 24.1.5
Java: JetBrains s.r.o. 17.0.6
OS: amd64 Windows 11 10.0
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.54
Live reload: Java unavailable (HotswapAgent): Front end unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Status