Changes between Initial Version and Version 1 of Ticket #14838


Ignore:
Timestamp:
Feb 19, 2012, 12:44:12 AM (9 years ago)
Author:
bill
Comment:

This deals with the focus manager (dijit/focus.js). Probably you want to connect to the actual focus/blur events on the widget. Does connecting for focus and blur on widget.focusNode (instead of widget) fix your problem?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14838

    • Property Owner set to rradian
    • Property Status changed from new to pending
    • Property Summary changed from dijit event firing order to dijit focus manager event firing order / delay
  • Ticket #14838 – Description

    initial v1  
    1 {{{
    21please see the attached html file.
    32
     
    98
    109tabbing thru the dijits yields:
     10{{{
    1111d1 dFocus:
    1212d1 dBlur Beg:
     
    2222d3 dBlur End:
    2323d4 dFocus: (the focus does end up on field 1 though)
     24}}}
    2425
    2526tabbing thru the html inputs yields:
     27{{{
    2628h1 hFocus:
    2729h1 hBlur: Beg
     
    3436  h1 hFocus:
    3537h3 hBlur End:
     38}}}
    3639
    3740changing a value in the first dijit box yields:
     41{{{
    3842d1 dFocus:
    3943d1 dBlur Beg:
     
    4145d2 dFocus:
    4246d1 dChange:
     47}}}
    4348
    4449changing a value in the first html box yields:
     50{{{
    4551h1 hFocus:
    4652h1 hChange:
     
    4854h1 hBlur End:
    4955d1 dFocus:
     56}}}
    5057
    5158the dijit firing order makes it impossible to enforce strict
    5259navigation rules based on field (or other) values or outcomes
    53 }}}