[External] : Re: Allow input controls to indicate significant user interaction

Michael Strauß michaelstrau2 at gmail.com
Mon Mar 27 18:32:07 UTC 2023


> I'd think a loss of focus might be considered as a trigger for "significant interaction".  Or perhaps you could give us an example of a use case in which it'll be insufficient?

For example, for a text field, gaining and losing focus is probably
sufficient to count as an interaction. Everything that happens between
gaining and losing focus can be thought of a as an operation in
progress.
The same isn't true for a slider: when we click-and-drag, the slider
should probably count as being interacted with as soon as the mouse
button is released, not when the slider loses focus (the same should
be true for key-press-and-hold).
Similarly, operations that are immediately completed (like pressing
the HOME or END keys on a slider) should most likely also immediately
count as a significant interaction.

It is true that I can do this without platform support, but it
requires me to hard-wire each type of control with its particular
behavioral details.


> It depends on the application requirements.  So, ultimately, the validation framework that the app developers are going to use must be flexible enough to handle all the cases.

Yes, and ideally, the third-party validation framework would work with
all kinds of controls (and even non-controls, as "Control" is a
concept that is only introduced with the javafx.controls module), not
only the standard controls that come with JavaFX.


More information about the openjfx-dev mailing list