You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Chris Bartlett (JIRA)" <ji...@apache.org> on 2010/08/25 16:12:16 UTC
[jira] Created: (PIVOT-610) Accordion & TabPane keyboard navigation
using COMMAND+n only works if the current Pane/Tab contains a focusable
Component
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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Sandro Martini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902490#action_12902490 ]
Sandro Martini commented on PIVOT-610:
--------------------------------------
Hi,
there is a specific reason why this can't be fixed before (for example in the 2.0 and maybe also in the 1.5.2) ?
Is it too complex to fix (but don't get me wrong, I'm only making a question ...) or other tickets have priority ?
I think that user interaction should have priority over others (secondary) ...
Bye,
Sandro
> 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.
[jira] Assigned: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Chris Bartlett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Bartlett reassigned PIVOT-610:
------------------------------------
Assignee: Chris Bartlett
> 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
> Assignee: Chris Bartlett
> Priority: Minor
> Fix For: 2.0
>
>
> 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.
[jira] Updated: (PIVOT-610) Accordion & TabPane keyboard navigation
using COMMAND+n only works if the current Pane/Tab contains a focusable
Component
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Brown updated PIVOT-610:
-----------------------------
Fix Version/s: (was: 2.0)
2.1
Moving to 2.1.
> 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
> Assignee: 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Chris Bartlett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902507#action_12902507 ]
Chris Bartlett commented on PIVOT-610:
--------------------------------------
I set it to a point version as it seemed to be a minor issue, but that was just a guess! I thought it better to assign something than to leave it blank.
I haven't looked into the problem in any detail, so can't estimate the effort for a fix or how it might impact.
It might require changes to the focus code, perhaps something as simple as recording the Container of the most recently focused Component when focus changes, so that it can then be used to send keypress events to that Container if when there is no longer a focused Component. However, it might also require changes to event propagation code.
Another approach might be to make Accordion & TabPane focusable, but that would most likely introduce other issues.
> 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.
[jira] Updated: (PIVOT-610) Accordion & TabPane keyboard navigation
using COMMAND+n only works if the current Pane/Tab contains a focusable
Component
Posted by "Sandro Martini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandro Martini updated PIVOT-610:
---------------------------------
Fix Version/s: 2.0
(was: 2.1)
> 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.0
>
>
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Sandro Martini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902777#action_12902777 ]
Sandro Martini commented on PIVOT-610:
--------------------------------------
Hi to all,
For me navigation in a RIA without mouse is a great time saver (mainly for non occasional users).
> 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.
Greg, what do you think it will be the effort to implementing this ? Is it simple so one of us can try to look, or do you prefer to make the change ?
In any case what do you think to re-target this for the 2.0 ?
And maybe IF simple to fix also for the 1.5.2 (I have never looked at the code for the focus implementation in Pivot, sorry) ?
Thanks,
Sandro
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Sandro Martini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902839#action_12902839 ]
Sandro Martini commented on PIVOT-610:
--------------------------------------
Ok, so I'll change its release to 2.0 (if too complex we can re-target later).
Bye
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902544#action_12902544 ]
Greg Brown commented on PIVOT-610:
----------------------------------
This isn't technically a bug, since it works as designed (it is valid for no component to have the focus). Also, in a real application, accordions and tab panes are unlikely to ever contain no focusable components, so this isn't something users are likely to run into.
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Chris Bartlett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902597#action_12902597 ]
Chris Bartlett commented on PIVOT-610:
--------------------------------------
Forgot to add this link to an example of a TabPane containing non-focusable components :)
http://pivot.apache.org/tutorials/tab-panes.html
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902836#action_12902836 ]
Greg Brown commented on PIVOT-610:
----------------------------------
If it is simple then I think we could move it to 2.0. I'd prefer to limit 1.5.x to trivial or show-stopper issues at this point. The more work we do on 1.5.x, the more testing we'll have to do, and the less time we will have to work on 2.0+.
> 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.
[jira] Commented: (PIVOT-610) Accordion & TabPane keyboard
navigation using COMMAND+n only works if the current Pane/Tab contains a
focusable Component
Posted by "Chris Bartlett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902595#action_12902595 ]
Chris Bartlett commented on PIVOT-610:
--------------------------------------
I wouldn't agree that these containers are unlikely to ever contain no focusable components on a pane/tab. Who knows what weird and wonderful apps Pivot might lead to?
Obviously it is valid for no component to have the focus, but I wouldn't expect the keypress handling of a container to appear to stop working merely because it is displaying read only data in Labels. I might choose to display categorised read-only data in various tabs or accordion panes.
I understand that this is down to the focus handling and event propagation within Pivot, but I see this as a limitation. If the framework was currently able to dispatch keypress events to the TabPane in the original scenario, I would be surprised if TabPane had been written in such a way as to ignore keypresses when displaying non-focusable children.
By all means change this ticket from a bug to a more appropriate JIRA type, such as improvement/wish.
> 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.