On 06/06/2019 17:14, [email protected] wrote:
On 6/5/19 4:31 PM, Sergey Bylokhov wrote:
On 05/06/2019 16:04, Semyon Sadetsky wrote:
I cannot find similar behavior of native components. What specifically do you
emulate?
I already point that a few emails before, On windows it use the native
components, on linux it emulate the motif library, only on mac it was
implemented as is, I guess it is most correct implementation.
Why motif on linux? Which of the supported OSes use it?
Because initial version of AWT on Linux used motif, and its replacement XAWT
was created to be compatible.
I've never saw such combo-box behavior on mac. Where I can see it?
I do not think that non-focusable components are wide used.
This popup cannot be opened by the keyboard and cannot be closed by the
keyboard, it is symmetric. It is similar to say unfocusable Button which cannot
be navigated nor pressed by the keyboard.
You probably need to read something about the UI accessibility principles
before fixing such bugs, because what you stated above just opposites to them.
You missed the point that we are not an application, but a library which
provides different things to the applications, it is up to the application to
use non-focusable components.
--
Best regards, Sergey.
