[ 
https://issues.apache.org/jira/browse/QUARKS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328004#comment-15328004
 ] 

ASF GitHub Bot commented on QUARKS-201:
---------------------------------------

GitHub user home4slc reopened a pull request:

    https://github.com/apache/incubator-quarks/pull/134

    QUARKS-201 added keyboard support to console

    Added tab indices to a lot of the html on the page and keypress handlers 
for some of the controls.
    Now the user can tab to open the hover for the job state and also tab (then 
push enter) to see all the properties in the graph.  Using the browser specific 
keys to close a popup/window will close the window containing the table.
    
    i.e, On MAC it is command + W

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/home4slc/incubator-quarks console_QUARKS_201

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/134.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #134
    
----
commit ac58f554ada12a3b54e8ef4500617829bcf8704e
Author: Susan L. Cline <[email protected]>
Date:   2016-06-09T22:52:19Z

    QUARKS-201 added keyboard support to console

----


> Make the quarks console keyboard navigible
> ------------------------------------------
>
>                 Key: QUARKS-201
>                 URL: https://issues.apache.org/jira/browse/QUARKS-201
>             Project: Quarks
>          Issue Type: Bug
>          Components: Console
>            Reporter: Susan L. Cline
>            Assignee: Susan L. Cline
>
> I think it's important that the console can be navigated with only the 
> keyboard.  My thoughts are for the 'View all oplet properties' table that it 
> be keyboard accessible as well since the graph itself can not be made 
> accessible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to