Opened 8 years ago
Closed 8 years ago
#12948 closed bug (invalid)
Date picker method destroy doesn't remove generated DOM id
Reported by: | serga84 | Owned by: | serga84 |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.datepicker | Version: | 1.11.3 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Here is my example how to fix it
var destroyMyDateTimePickers = function () {
'use strict';
$('.datetimepicker, .datepicker').each(function () {
var $this = $(this);
if (!($this.attr('readonly') $this.attr('disabled'))) {
$this.datepicker("destroy");
jQuery UI Date Picker bug. Date picker doesn't remove generated DOM id. if ($this.attr('id').indexOf('dp') === 0) {
$this.removeAttr('id');
}
}
});
};
Change History (2)
comment:1 Changed 8 years ago by
Owner: | set to serga84 |
---|---|
Status: | new → pending |
comment:2 Changed 8 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Datepicker doesn't add an id to the element, so I'm not sure what you're referring to. If you can provide a reduced test case that shows the problem, we can look into it, but I have a feeling whatever you're seeing is related to the time extension you're using.