Changes between Initial Version and Version 3 of Ticket #3648


Ignore:
Timestamp:
Jul 10, 2007, 7:56:40 AM (12 years ago)
Author:
bill
Comment:

I split this bug up into keyboard support (#3655) and general clicking support (this bug).

Basically what we need is onBlur and onFocus events on widgets, rather than on dom nodes. Shifting focus from one dom node to another node inside the same widget, or even switching from the widget to the dropdown (and back again), shouldn't cause such an onBlur event, because conceptually you are still inside the widget.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3648

    • Property Status changed from new to assigned
    • Property Severity changed from major to normal
    • Property Component changed from Dijit to Accessibility
    • Property Summary changed from Regression in [9508]: no cancelling if autoSave=true to InlineEditBox: need to cancel or save onblur (if autoSave=true)
    • Property Priority changed from high to normal
  • Ticket #3648 – Description

    initial v3  
    11In the topmost inline textbox in test_InlineEditBox, if you click the text to edit there is no way to cancel the edit; the textbox "sticks" on blur unless/until you change the value to something else, after which it behaves as expected.
    22
    3 Before [9508] users had the option to cancel a change.  Now they don't, and they probably should.
     3Clicking outside the edit widget or it's dropdown (an effective onBlur *on the widget*) should cause the current changes to save, or if no changes were made, should cause a cancel.
     4
     5(But see related bug #3655 about canceling via the keyboard)
     6
     7