Skip to main content

Search and Top Navigation

#3338 closed bug (fixed)

Opened September 10, 2008 06:51PM UTC

Closed September 20, 2008 07:06AM UTC

Last modified October 11, 2012 09:15PM UTC

Big datepicker bug with IE and no id on the attached input element

Reported by: skoon Owned by: grabanski
Priority: major Milestone:
Component: ui.datepicker Version: 1.5.2
Keywords: Cc:
Blocked by: Blocking:

I'm seeing a bug using the datepicker that appears to be related to

having at least two input elements with datepickers attached that have

no id attribute specified.

Using the following HTML/Script

<script type="text/javascript" src=""></


<script type="text/javascript">

// Load jQuery

google.load("jquery", "1.2.6");

google.load("jqueryui", "1.5.2");




<div id="first"><input type="text"></div>

<div id="second"><input type="text"></div>

<script type="text/javascript">


function init() {

$("#first > :input").datepicker({ showOn: "button", buttonImage:

"calendar.gif", buttonImageOnly: true});

$("#second > :input").datepicker({ showOn: "button", buttonImage:

"calendar.gif", buttonImageOnly: true});




Clicking on the calendar button on the second input and selecting a

date will cause the first input element to be populated with the

selected date in IE6/IE7.

Attachments (0)
Change History (2)

Changed September 20, 2008 07:06AM UTC by kbwood comment:1

resolution: → fixed
status: newclosed

Fixed. Assigned ID was set by time to the millisecond, which could result in two fields getting the same ID. IDs are now sequential.

Changed October 11, 2012 09:15PM UTC by scottgonzalez comment:2

milestone: TBD

Milestone TBD deleted