#3611 closed task (fixed)
Spinner, Slider: flag to control when onChange is called
| Reported by: | bill | Owned by: | Douglas Hays |
|---|---|---|---|
| Priority: | high | Milestone: | 0.9 |
| Component: | Dijit - Form | Version: | 0.9 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description (last modified by )
By default spinner and slider should only report onChange() when the user tabs away etc (see #3609), but I guess there should be a flag to have it reported as you move the handle (in Slider) or do the up/down buttons (for Spinner).
This will let spinner and slider be used in InlineEdit? with auto-save feature (#3514)
Change History (5)
comment:1 Changed 15 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 15 years ago by
Furhter investigation with FF and IE shows that clicking slider buttons and clicking the bar to position the slider removes focus from the handle and thus will fire onChange events.
comment:3 Changed 15 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | Spinner, Slider: flag to control when onValueChanged is called → Spinner, Slider: flag to control when onChange is called |
comment:4 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Seems to be fixed by [9627]. All form widgets can set the boolean this.intermediateChanges.
comment:5 Changed 11 years ago by
| Component: | Dijit → Dijit - Form |
|---|
Note: See
TracTickets for help on using
tickets.
This request may have to be amended for slider since browsers like Safari do not honor tabIndex on div elements. Thus there will not be any blur events to trigger the onChange to fire. On Safari, I think slider will need to fire on all change activity.