Skip to main content

Search and Top Navigation

#12948 closed bug (invalid)

Opened June 01, 2015 11:29AM UTC

Closed June 18, 2015 08:46AM UTC

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');

}

}

});

};

Attachments (0)
Change History (2)

Changed June 01, 2015 11:57AM UTC by scottgonzalez comment:1

owner: → serga84
status: newpending

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.

Changed June 18, 2015 08:46AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

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!