Opened 10 years ago
Last modified 7 years ago
#8907 open bug
Datepicker: Calling a method on a datepicker while another datepicker is open causes issues
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.datepicker | Version: | 1.9.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description (last modified by )
When the user double-clicks to select a date from the DatePicker tool on #datepicker1, the "defaultDate" setting on #datepicker2 is causing the actual field value to be set to the current date. When I step through the code, this does not happen. It only happens when not in debug mode.
Change History (10)
comment:2 Changed 10 years ago by
| Description: | modified (diff) |
|---|---|
| Status: | new → open |
Reduced: http://jsfiddle.net/nwpq7/5/
comment:3 Changed 10 years ago by
| Milestone: | 1.10.0 → none |
|---|
comment:4 Changed 8 years ago by
| Summary: | DatePicker Double-Click Issue with setting defaultDate on Another DatePicker → Datepicker: Calling a method on a datepicker while another datepicker is open causes issues |
|---|
What happens is that calling a method on datepicker 2 while datepicker 1 is open causes datepicker 2 to be rendered in place of datepicker 1. You can see this happening by selecting a date in a different month for datepicker 2, then selecting a date in datepicker 1; you'll see the month switch as the datepicker is closing.
comment:10 Changed 7 years ago by
Replying to scottgonzalez:
So is there any ways to prevent it from happening?
Sorry, first time user. Here's the code on jsFiddle: http://jsfiddle.net/nwpq7/3/