Fluid Infusion

Can't use the "Tab" key to navigate out of reorderable tabs

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Cannot Reproduce
  • Affects Version/s: 0.4beta1, 0.4, 0.5beta1, 0.5, 0.6beta1, 0.6, 0.7, 0.8, 1.0, 1.1, 1.1.1, 1.1.2, 1.2
  • Fix Version/s: 1.3
  • Component/s: Reorderer
  • Labels:
    None
  • Environment:
    FF2, Opera 9.6 (Mac OS 10.5, WinXP)

Description

You are able to use the "Tab" key to navigate into the set of reorderable tabs, but are not able to use the "Tab" key to leave them.

For FF2 on WinXP you are able to use the arrow keys to navigate away from the set of reorderable tabs, after pressing the "Tab" key a second time.

Test Site: http://build.fluidproject.org/sakai-imagegallery-tool/sample-code/reorderer/jquery-tabs/jquery-tabs.html

Issue Links

This issue is duplicated by:
FLUID-862 Cannot use the keyboard to navigate away from the reorderable jQuery tabs, using ff Major Closed
FLUID-1185 cannot use the keyboard to navigate away from sortable jQuery Tabs, using Opera 9.5 Major Closed
This issue relates to:
FLUID-1185 cannot use the keyboard to navigate away from sortable jQuery Tabs, using Opera 9.5 Major Closed
FLUID-861 Cannot tab off of accessible jQuery tabs: using FF Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Antranig Basman added a comment -
Fixed at revision 5567
Show
Antranig Basman added a comment - Fixed at revision 5567
Hide
Permalink
Justin Obara added a comment -
Tested in (FF2, Opera 9.5 (Mac OS 10.5, WinXP) and the issue still occurs.
Show
Justin Obara added a comment - Tested in (FF2, Opera 9.5 (Mac OS 10.5, WinXP) and the issue still occurs.
Hide
Permalink
Antranig Basman added a comment -
This has been investigated in some detail now, with no real understanding of the issue emerging. There is a possibility that the particular markup used here is implicated - that is, an anchor tag within the <li> which occupies more physical space than its parent. Basically a tab order cycle results, with the next focus target after the active tab being considered the container itself, possibly via the intermediate of the anchor. An interesting focus effect has been observed on FF2 whereby a container with tabindex is considered focused if one of the elements within it are focused. This is particularly visible in the portal sample - putting focus onto one of the dropdowns for example on the top right portlet.

There was an experimentation with a "dynamic tabindex" version of the keyboard accessibility plugin, but this appears to create more instability in focus than it resolves.
Show
Antranig Basman added a comment - This has been investigated in some detail now, with no real understanding of the issue emerging. There is a possibility that the particular markup used here is implicated - that is, an anchor tag within the <li> which occupies more physical space than its parent. Basically a tab order cycle results, with the next focus target after the active tab being considered the container itself, possibly via the intermediate of the anchor. An interesting focus effect has been observed on FF2 whereby a container with tabindex is considered focused if one of the elements within it are focused. This is particularly visible in the portal sample - putting focus onto one of the dropdowns for example on the top right portlet. There was an experimentation with a "dynamic tabindex" version of the keyboard accessibility plugin, but this appears to create more instability in focus than it resolves.
Hide
Permalink
Justin Obara added a comment -
Bug Parade: 0.5 release
Show
Justin Obara added a comment - Bug Parade: 0.5 release
Hide
Permalink
Antranig Basman added a comment -
This issue needs to be escalated to Mozilla - from what I can recall of the investigation, we seemed to verify that the issue was not dependent on any Javascript which was fired during the tab keypress, therefore it has to be a defect in the browser. If it doesn't occur in FF3, that just leaves Opera...
Show
Antranig Basman added a comment - This issue needs to be escalated to Mozilla - from what I can recall of the investigation, we seemed to verify that the issue was not dependent on any Javascript which was fired during the tab keypress, therefore it has to be a defect in the browser. If it doesn't occur in FF3, that just leaves Opera...
Hide
Permalink
Jonathan Hung added a comment -
No longer appears to be an issue. Tested Dec 9, 2010 on FF3.6 and IE8, Windows.
Show
Jonathan Hung added a comment - No longer appears to be an issue. Tested Dec 9, 2010 on FF3.6 and IE8, Windows.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
1d
Original Estimate - 1d
Remaining:
1d
Remaining Estimate - 1d
Logged:
Not Specified
Time Spent - Not Specified
Atlassian JIRA (v4.4#649-r158309) | Report a problem
Powered by a free Atlassian JIRA open source license for The FLUID Project. Try JIRA - bug tracking software for your team.