Custom Query (7259 matches)
Results (64 - 66 of 7259)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1880 | fixed | Datepicker: should position itself so it is always visible | ||
| Description |
The datepicker (v3.0) does not position itself so it is always visible to users. Ideally, information about the user's browser window, the desired launch position, and the size of the calendar could be used to position the calendar such that it is always visible. |
|||
| #1881 | fixed | UI Datepicker v3.0 with other libraries | ||
| Description |
UI Datepicker v3.0 fires js error when jQuery.noConflict() is used to prevent conflict with other libraries: $(this).addClass is not a function |
|||
| #1885 | fixed | datepicker: date range bug | ||
| Description |
Here is a video of the bug http://screencast.com/t/zrdTeJ0i This is a bug that was present in 2.7 and was reported in your comments as 90 and 91 First when I select a date in the first field I can pick an earlier date in the second field, when I should be restricted to using a later date. Second when I go back to the first date field and open the date picker the date is not the month I picked. From what I can tell it opens the month based off of the day of the second month. This has been confirmed on multiple computers in both FF 2.0.0.9 and IE 7 |
|||