You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many ways to treat 'anything got changed'. First, you have many events (not only keyup) that can affect content of a text field. For example, you can select a portion of text and remove it using context menu, you can paste text from clipboard, etc. Second, reacting on every little change in some cases might be an overhead, so user may want to get change events afer some delay. Since there are plenty of different cases with different requirements, I decided not to trying to support them all in core framework. A user can create its own component (see documentation) which behaves exactly as expected. I would extend Flavour to support more different cases of changing, but I don't like quick and dirty solutions, a framework must be flexible enough. So I need first to think about this, analyze different use cases, look how other frameworks (Angular, React) handle this, etc. Unfortunately, not in near future. Frankly speaking, I don't have time to support Flavour, and I rarely fix critical bugs. I'm focused on pure TeaVM now, sorry.
Ok good to know that is kinda unmaintained. I'm currently investigating what technology to use for my ecommerce storefront. I liked flavour, but I'm probably going for my own UI toolkit (https://github.com/mojo2012/jfly, just in case your wondering).
I wanted to bind a value of an
input
to a field in my view. First I though this should work:But the value is only updated when I hit "return" (same as the real html change event).
I solved this using this html:
Together with this java code:
But it would be nice if the html:change or the html:bidir-value would do exactly that -> update the value on change not just after hitting return.
The text was updated successfully, but these errors were encountered: