Far0n

I also find the current behavior a bit inconvenient, because of the `Trigger=True` side effects (see also: https://github.com/h2oai/wave/discussions/952). This PR here by @zillionare looks similar to one of my workarounds,...

Also discussed: **Syntax sugar for change detection and propagation** , something like: ```python def on_change( arg: str = None, predicate: Optional[Callable] = None, compared_to: str = "client", propagate: bool =...

It seems vertically centered in the browser. That works most of the time just fine, but somtimes I would like it to move a bit up: Here, I would like...

@mturoci It can easily look a bit off (imho) if center of mass of the app's cards is significantly above the screen center:  I like this better: 

idk, for me dialogs just too far down: 

would be nice to allow it to place here (middle of red cross): 

kk, let's close this here then?

Happy to help with the documentation. Guess starter would be to update the doc-string of `def on`, but what are other places?

concerns about `sort_args` approach (for reference): https://github.com/h2oai/wave/discussions/1480#discussioncomment-2888734 https://github.com/h2oai/wave/discussions/1480#discussioncomment-2888943

Maybe it would be better for now to recommend to use **on** only for buttons. `sort_args` wont be needed then and it doesn't solve other tricky cases like trigger=True on...