Changes between Initial Version and Version 2 of Ticket #15132


Ignore:
Timestamp:
Apr 5, 2012, 3:17:28 PM (8 years ago)
Author:
Douglas Hays
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15132

    • Property Owner changed from Douglas Hays to bill
    • Property Status changed from new to assigned
    • Property Component changed from Dijit - Form to Dijit
    • Property Milestone changed from tbd to 1.7.3
  • Ticket #15132 – Description

    initial v2  
    1 You should be able to see onmousedown followed by onfocus (or _onFocus).  But since dijit/focus.js uses the capture=truye falg, and then calls _onFocus from the mousedown handler, event handlers waiting on the mousedown see the _onFocus first (and this.focused=true) before seeing the mousedown event.  This is causing the failure in robot/ValidationTextBox (placeholder::type in textbox).  Chrome and Firefox won't focus the widget's focusNode automatically on mouse down and without seeing the mousedown event before focus, then I don't know where I should manually change the focus or not.  This needs to be fixed in 1.7.3 since it worked OK in 1.7.2.  Since then, _FormWidgetMixin is looking for the focus after onmousedown.
     1You should be able to see onmousedown followed by onfocus (or _onFocus).  But since dijit/focus.js uses the capture=true flag, and then calls _onFocus from the mousedown handler, event handlers waiting on the mousedown see the _onFocus first (and this.focused=true) before seeing the mousedown event.  This is causing the failure in robot/ValidationTextBox (placeholder::type in textbox).  Chrome and Firefox won't focus the widget's focusNode automatically on mouse down and without seeing the mousedown event before focus, then I don't know ifI should manually change the focus or not.  This needs to be fixed in 1.7.3 since it worked OK in 1.7.2.  Since then, _FormWidgetMixin is looking for the focus after onmousedown.