Custom Query (7259 matches)
Results (106 - 108 of 7259)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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 |
|||
#1883 | wontfix | slider() cannot be applied to JQuery objects that are not yet in DOM | ||
Description |
The following test case fails with an obscure JQuery error message ("elem.style has no properties" on jquery.js:698): <div id = "placeholder"></div> <script type = "text/javascript"> $(document).ready(function() { $('<div class = "ui-slider-1">' + '<div class = "ui-slider-handle"></div>' + '</div>').slider().appendTo('#placeholder'); }); </script> This attempts to create a new JQuery object from HTML, turn it into a slider, and then add it to the DOM. If I reverse the order of those calls, appending it into the DOM first and then turning it into a slider, it works fine: <div id = "placeholder"></div> <script type = "text/javascript"> $(document).ready(function() { $('<div class = "ui-slider-1">' + '<div class = "ui-slider-handle"></div>' + '</div>').appendTo('#placeholder').slider(); }); </script> I'm not sure if you need to support this, since the workaround is simple. But if not, it should be clearly documented on the Slider's documentation page. It took me a while to track down because the error message is so inscrutable... |
|||
#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 |