[
https://issues.apache.org/jira/browse/FLEX-33772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792882#comment-13792882
]
Cosma Colanicchia edited comment on FLEX-33772 at 10/11/13 6:03 PM:
--------------------------------------------------------------------
I think that the behavior is correct, and it is a direct consequence of keeping
the old behavior of shift-tabbing to the *last* unselected element of the group.
When forward-tabbing away from the big button, the logic have no choice but
assume that you are in "forward tab" sequence (since the only available
information is direction and current focus, previous focus history is lost),
thus assuming that focus has already gone through "A" (that is the wanted focus
target in the group when forward tabbing with no group selection).
In other words, the said choice naturally produces different tab sequences when
moving forward or backward, thus, when inverting the direction, it is very
possible that focus is not set to the previously focus element. I think it is
logically unavoidable, unless we want to "remember" how we did get to the
current focused element (I hope not).
was (Author: cosmacol):
I think that the behavior is correct, and it is a direct consequence of keeping
the old behavior of shift-tabbing to the *last* unselected element of the group.
When forward-tabbing from the bottom, the logic have no choice but assume that
you are in "forward tab" sequence (since the only available information is
direction and current focus, previous focus history is lost), thus assuming
that focus has already gone through "A" (that is the wanted focus target in the
group when forward tabbing with no group selection).
In other words, the said choice naturally produces different tab sequences when
moving forward or backward, thus, when inverting the direction, it is very
possible that focus is not set to the previously focus element. I think it is
logically unavoidable, unless we want to "remember" how we did get to the
current focused element (I hope not).
> Incorrect tab focus behavior (closed loops) when using focus groups (such as
> RadioButton components)
> ----------------------------------------------------------------------------------------------------
>
> Key: FLEX-33772
> URL: https://issues.apache.org/jira/browse/FLEX-33772
> Project: Apache Flex
> Issue Type: Bug
> Components: Focus Manager
> Affects Versions: Apache Flex 4.11.0
> Reporter: Cosma Colanicchia
> Assignee: Alex Harui
> Priority: Minor
> Labels: patch
> Fix For: Apache Flex 4.11.0
>
> Attachments: FocusManager.patch, FocusManager.patch,
> FocusManager-revised-2.patch, FocusManager-revised.patch, TestFocus.air,
> TestFocus-current.air, TestFocus.mxml, TestFocus.mxml, TestFocus-patched.air,
> TestFocus-patched-revised.air, TestFocus-screenshot.png,
> TestFocus-updated.mxml
>
>
> When additional components that are not part of the focus group are
> positioned between two group elements, it may be impossible to move the focus
> away from the group using the keyboard.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
