Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Hi, Shashi. I checked it on the fresh build of jdk/client, and confirm that it is possible to select progress bar using ctrl+option+up/down/left. Screenshot is attached to the bug. On 04/11/2018 23:08, shashidhara.veerabhadra...@oracle.com wrote: Hi Sergey, I enabled 'All controls' access in

Re: [12] RFR JDK-8198334: java/awt/FileDialog/8003399/bug8003399.java fails in headless mode

Hi, Prasanta. In the log of Test8173145 the ClassCastException exists as well: https://bugs.openjdk.java.net/browse/JDK-8198334?focusedCommentId=14157839=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14157839 On 07/11/2018 01:29, Prasanta Sadhukhan wrote: Hi

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Hi Shashi, I ran a test with a native dialog-based Windows app with two progress bars. I used the built-in Narrator as the accessibility tool in Windows 10. When using Tab key to navigate between controls on a dialog box, the progress bar without WS_TABSTOP style cannot be focused; the one

Re: RFR 8186549: move ExtendedRobot closer to tests

Phil, Igor, A quick check shows that indeed most of cases where a “lib” library used by relative path (which may or may not be the top level library) are in the client tests. $ egrep -r '@library.* (../)+lib' --include "*.java" . | cut -d ':' -f 1 | cut -d / -f 2-3 | uniq -c 59 java/awt

Re: [12] RFR JDK-8213181:Updation of ProblemList.txt for removal of passing swing test

On 07/11/2018 21:44, Prasanta Sadhukhan wrote: I found that these tests are passing when ran for 100 iterations on windows javax/swing/plaf/basic/Test6984643.java It is necessary to check the code of the tests as well, for example the test above was reported in JDK-8198340. The reason is that

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Hi Sergey, Probably we should stick with generic keys to go thro' java components like the TAB key traversals. Because on Windows, I just can't get focus onto the progress bar without explicitly setting the focusable to true(like in fix). Ctrl+option+up/down/left/right is specific to the

Re: [12] RFR JDK-8213181:Updation of ProblemList.txt for removal of passing swing test

Since some of the tests are marked generic-all and it's difficult to run 100 iterations on all platforms, I concentrated on the tests that are marked failing on one platform. I found that these tests are passing when ran for 100 iterations on windows

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

On 07/11/2018 22:12, Shashidhara Veerabhadraiah wrote: Hi Sergey, Probably we should stick with generic keys to go thro' java components like the TAB key traversals. Because on Windows, I just can't get focus onto the progress bar without explicitly setting the focusable to true(like in fix).

Re: [12] RFR JDK-8213181:Updation of ProblemList.txt for removal of passing swing test

On 08-Nov-18 11:52 AM, Sergey Bylokhov wrote: On 07/11/2018 21:44, Prasanta Sadhukhan wrote: I found that these tests are passing when ran for 100 iterations on windows javax/swing/plaf/basic/Test6984643.java It is necessary to check the code of the tests as well, for example the test

[12] Review Request: 8213110 Remove the use of applets in automatic tests

Hello. Please review the fix for jdk 12. Bug: https://bugs.openjdk.java.net/browse/JDK-8213110 Webrev: http://cr.openjdk.java.net/~serb/8213110/webrev.03 Description of the bug: A number of our tests in jdk still launch by applets via "@run applet". Usually we drop this usage when we update

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Hi Alexey, Thanks for running the test on Windows. With accessibility in question we should reach the component using the keyboard only. Touch and mouse is not permitted. So the question is can it be reached via a keyboard stroke? If not then that component is not accessible and that's the

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

On 07/11/2018 11:42, Alexey Ivanov wrote: Narrator does not work with Java apps: it sees only the top-level window of SwingSet2. It is still unsupported =(, we need to check the jaws first using their shortcuts: https://www.freedomscientific.com/Content/Documents/Manuals/JAWS/Keystrokes.txt

Re: [12] JDK-7124285: Nothing heard from VoiceOver regarding the status of the progress bar

Hi Sergey, If that's the case, then the solution should work considering all the variations in the a11y tool set across the different platforms. Isn't it? So considering that, the proposed solution works for all the different tool set(TAB and Ctrl+Option) across the platforms and without it, it

Re: [12] RFR JDK-8213181:Updation of ProblemList.txt for removal of passing swing test

On 08-Nov-18 11:59 AM, Prasanta Sadhukhan wrote: On 08-Nov-18 11:52 AM, Sergey Bylokhov wrote: On 07/11/2018 21:44, Prasanta Sadhukhan wrote: I found that these tests are passing when ran for 100 iterations on windows javax/swing/plaf/basic/Test6984643.java It is necessary to check the

Re: [12] RFR JDK-8198334: java/awt/FileDialog/8003399/bug8003399.java fails in headless mode

Hi Sergey, Actually, I was more concerned about the swing test failure com/sun/java/swing/plaf/windows/Test8173145 which I guess is failing with HeadlessException. I can create a separate bug for this test alone and handle this tag addition in the test case w.r.t that bug. Will that be fine?