On Wed, 6 Apr 2022 10:18:36 GMT, Alexey Ivanov <aiva...@openjdk.org> wrote:
>> It is impossible right now to manipulate state of the accessible children of
>> the JTabbedPane via their AccessibleValue and because of that some of the
>> assistive technologies are unable to interact with the parts of the
>> JTabbedPane - namely, buttons, representing the JTabbedPane panel navigation
>> buttons. Magnified is just one of the examples that can be engaging without
>> connecting the hardware such as eye movement tracker.
>>
>> By adding AccessibleValue to the JTabbedPane children containers we
>> eliminate is problem. And since this inner class is private the standard
>> review should be sufficient, no CSR is required.
>
> test/jdk/javax/accessibility/JTabbedPane/AccessibleTabbedPaneTest.java line
> 39:
>
>> 37: public class AccessibleTabbedPaneTest {
>> 38: public static void main(String[] args) {
>> 39: JTabbedPane pane = new JTabbedPane();
>
> Shouldn't this be run on EDT?
I do not see why. I am only working with the data model and only set the data
model state trough the appropriate calls, they do not rely on any asynchronous
processing or external events.
-------------
PR: https://git.openjdk.java.net/jdk/pull/8049
