[
https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902717#action_12902717
]
Greg Brown commented on PIVOT-610:
----------------------------------
OK, those are good points. However, if no component has the focus, then there's
no way for an Accordion or TabPane to get keyboard events (by definition, key
events are dispatched to the component that has the focus, and are propagated
up the hierarchy from there).
A possible solution to this might be for the container to take the focus after
unsuccessfully attempting to set it on the selected panel or tab.
> Accordion & TabPane keyboard navigation using COMMAND+n only works if the
> current Pane/Tab contains a focusable Component
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: PIVOT-610
> URL: https://issues.apache.org/jira/browse/PIVOT-610
> Project: Pivot
> Issue Type: Bug
> Components: wtk, wtk-terra
> Affects Versions: 1.5.1
> Environment: n/a
> Reporter: Chris Bartlett
> Priority: Minor
> Fix For: 2.1
>
>
> Users can navigate around the panes/tabs of Accordion and TabPane by pressing
> the system specific command modifer key plus a number from 1 to 9.
> On MS Windows this would mean CTRL+1 to CTRL+9 selecting the 1st to 9th
> pane/tab respectively.
> These keypresses are only processed if a child component of the container has
> focus.
> A TabPane might have 2 Tabs
> Tab 1 - contains an enabled TextInput
> Tab 2 - contains an enabled Label
> If the TextInput on Tab 1 has focus, it is possible to change to Tab 2 by
> pressing CTRL+2, but once there, it is not possible to get back to the Tab 1
> by pressing CTRL+1.
> This is because Labels are not focusable, and by default Pivot Containers are
> not focusable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
