Opened 15 years ago
Closed 15 years ago
#2859 closed bug (worksforme)
Datepicker 3.4.3 'change' commits changes to all datepickers
Reported by: | mnichols | Owned by: | grabanski |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | ui.datepicker | Version: | 1.5b4 |
Keywords: | datepicker 3.4.3 change | Cc: | |
Blocked by: | Blocking: |
Description
When trying to use the 'change' function, the new settings are applied to all datepickers on page. For example, with the code below, one would expect that only the input 'myrange' would be a ranged datepicker, but in fact it causes all pickers to become range-aware. If this is by design it should be made clearer.
To test: <input type="text" class="date" id="plainoledate"/> <script type="text/javascript"> $(document).ready(function(){ $('.date').datepicker(); }); </script> <input type="text" class="date" id="myrange"/> <script type="text/javascript"> $(document).ready(function(){ $('#myrange').datepicker('change',{ rangeSelect: true}); }); </script>
Change History (4)
comment:1 Changed 15 years ago by
Milestone: | 1.2.4 |
---|
comment:2 Changed 15 years ago by
Component: | ui.core → ui.datepicker |
---|---|
Owner: | paul deleted |
Version: | 1.2.3 → 1.5b4 |
comment:3 Changed 15 years ago by
Owner: | set to grabanski |
---|---|
Status: | new → assigned |
comment:4 Changed 15 years ago by
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
I tested your sample code, as well as a few other settings, against latest SVN and couldn't reproduce this problem. If you continue to experience this problem after upgrading to latest SVN, feel free to re-open this ticket.
Milestone 1.2.4 deleted