On Thu, 20 May 2021 06:56:10 GMT, Pankaj Bansal <pban...@openjdk.org> wrote:
> Is there a reason it is not causing an issue in case if JList? JList also has > elements inside a container, but I see that we can navigate the elements in > JList though there is also one issue that the VO always says "1 on n" (n is > total number of elements) on selecting any element of list. I am just > wondering why is this only needed for combobox and other components seem to > work fine. It is by far is not limited with JList. It also affects menu navigation with the accessibility shortcuts - in open menu with AS we can'[t walk past first item. It is particularly bad in JList because traversing trough JList causes a lot of events to be generated such as selection/deselection of the list elements, focus change and such. This causes OS to re-evaluate the current selection by asking either container or child about the current selection index and that is what generates so fierce special effect of multiple selection and selections changing because depending on the order in which system events got populated and developed we update selection in different (but always incorrect) order. ------------- PR: https://git.openjdk.java.net/jdk/pull/4084
