Skip to main content

Search and Top Navigation

#8702 closed bug (notabug)

Opened October 19, 2012 01:15PM UTC

Closed October 19, 2012 02:45PM UTC

Datepicker + Min/Max Range + UI Button

Reported by: cautionbug Owned by:
Priority: minor Milestone: 1.10.0
Component: ui.datepicker Version: 1.9.0
Keywords: Cc:
Blocked by: Blocking:

For starters, i'm brand new to bug tracking here. i did search for this issue, but didn't really expect to find any hits.

Since Datepicker doesn't provide access to a UI-themed button trigger, i found a workaround for it:


\\\\(yes, my comment at the bottom)

The workaround is fine. The datepickers are set up, and in most cases work well. However, when i tried using a range setup as shown in the demos, selecting a date on one input took the UI off the other input's trigger button.



The commented lines of JS in the "onSelect" callbacks is how i've worked around the problem in the workaround.

i get the sense that the "onSelect" callback which changes the sibling datepicker's option is actually destroying & re-creating the sibling with the new option. Is this how it works for all option update calls? If so, i guess the workaround's workaround is my only option since the button is "buttonized" after the datepicker. However, it seems by now there would be an option to provide a UI-themed trigger button from the datepicker's options.</whine>

Attachments (0)
Change History (1)

Changed October 19, 2012 02:45PM UTC by mikesherov comment:1

resolution: → notabug
status: newclosed

Hi, and thanks for contributing! Unfortunately, the bug tracker isn't the place for posting questions about using jquery-ui. I suggest you start you search in or on stackoverflow or IRC to see if someone could help you out. If you still believe after doing all that, that you have a legit bug, please come back and post it. Until then, I'm closing this as "not a bug".