On Thu, 8 Dec 2022 12:46:48 GMT, Alexander Zuev <kiz...@openjdk.org> wrote:
>>> > If that is not possible I suggest providing that functionality so >>> > applications will be able to use that. Probably even provide some >>> > predefined cursors, like "faded"/"blurred"/nonblinked/etc. That could be >>> > configured per L&F as well. >> >>> That would be a nice feature to have but right now we have an issue where >>> default behaviour of the component defies the VPAT guidelines. >> >> I am not sure that changing the default behavior of all text >> components(including embedded to other components) to use a non-blinking >> cursor is a good idea, you can convince me if you find someone who uses the >> same approach, any applications? Probably at least for the native look&feels >> we can use the same behavior as the native default components >> win32/cocoa/gtk. > >> someone who uses the same approach, any applications > > Gnome on Ubuntu 22, default applications. Editable text components have > blinking carets, non-editable - non-blinking ones. I agree with @azuev-java. A caret — blinking or not — is better than no caret at all. The caret not only visually shows the focus owner (a non-editable text component) but also facilitates text selection (with keyboard). ------------- PR: https://git.openjdk.org/jdk/pull/11408
