#3516 closed bug (fixed)
DatePicker: Safari can't handle multiple inputs without IDs
| Reported by: | andersonic | Owned by: | grabanski |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | ui.datepicker | Version: | 1.5.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
On Safari 3.1.2 for Mac, if more than one input is turned into a datepicker, and neither has pre-set IDs, setting a date in any of them will set the date in the first one.
<input type="text" name="date1" class="datePick" />
<input type="text" name="date2" class="datePick" />
$(".datePick").datepicker()
This can be worked around by giving the inputs ID attributes.
Note: See
TracTickets for help on using
tickets.
Generated IDs were based on timestamp, so both of these would have received the same ID. Fixed in 1.6 with a sequential number as part of the generated ID.