FLUID-1600: Pressing the "Tab" key to exit edit mode, places focus on the wrong item

Metadata

Source
FLUID-1600
Type
Bug
Priority
Major
Status
Open
Resolution
N/A
Assignee
N/A
Reporter
Justin Obara
Created
2008-09-22T10:47:28.000-0400
Updated
2016-11-15T09:11:26.465-0500
Versions
  1. 0.5beta1
  2. 0.5
  3. 0.6beta1
  4. 0.6
  5. 0.7
  6. 0.8
  7. 1.0
  8. 1.1.1
  9. 1.2
  10. 1.2.1
  11. 1.3
  12. 1.4
  13. 1.5
  14. 2.0
Fixed Versions
N/A
Component
  1. Inline Edit

Description

Pressing the "Tab" key to exit edit mode, places focus on the wrong item

Steps to reproduce:

1) Open the Simple Text Inline Edit example from the daily build site:
http://build.fluidproject.org/infusion/demos/inlineEdit/simple/html/inlineEdit.html

2) Open first inline edit field - the Title - and change the value

3) Using the keyboad press the "Tab" key to exit edit mode

Notice that focus isn't placed on the "Undo" link but on the next tabbable item - in this case, the caption field.

Environments

FF2, FF3, Opera 9.6, Safari 3 (Mac OS 10.5)
Safari 5 (Mac OS 10.6)
FF4 (Mac OS 10.6)
FF2, FF3, IE6, IE7, IE8, Opera 9.6 (Win XP)
FF3, IE7, IE8 (Win Vista)
FF3, IE6 (Win 2000)

Comments

  • Justin Obara commented 2008-09-22T12:50:54.000-0400

    Bug Parade: 0.5 release

  • Antranig Basman commented 2008-11-03T14:07:28.000-0500

    I am not sure this will be easy to resolve at all. The default browser behaviour appears to be to compute the next tab control at the point of event handling. Creating or removing an element with tabindex in the oncoming focus path does not make the browser change its mind. Therefore it would seem extremely hard to encourage the browser to tab to a control that is not visible at the time the key is pressed.

    The only way out I can think of, is to hijack the processing of tab order 100% - to have a model of the document separate from the static tabindex/control order which is delegated to when tab is pressed on an "owned" component. This would be quite expensive, as it would require perpetual DOM scans, but it might promise to resolve not only this issue, but a number of other portability concerns such as FLUID-861. It seems a somewhat drastic step though.

  • Justin Obara commented 2008-11-04T13:31:30.000-0500

    design-watched

  • Jess Mitchell commented 2010-12-20T16:31:42.793-0500

    This happens the first time there is an edit. If you Shift+Tab back to the edit field, edit again, press tab, it does go to the undo/redo.