> I'm seeing a bug using thedatepickerthat appears to be related to > having at least two input elements with datepickers attached that have > no id attribute specified.
One thing I've noticed about datepicker is that it seems to work based on the id of the bound element, rather than just being bound to the element itself. I'm sure there's a very good reason for it, but because of that it's a good idea to make sure that each imput element gets a unique ID, which takes a little extra work if you are adding a field dynamically, cloning fields and the like. -- Josh ----- Original Message ----- From: "Jon L" <[EMAIL PROTECTED]> To: "jQuery UI" <[email protected]> Sent: Friday, October 10, 2008 2:59 PM Subject: [jquery-ui] Re: Big datepicker bug with IE and no id on the attached input element I was also having the same trouble with 2 datepicker inputs next to each other where selecting the date from the second input changed the value of the first input instead of updating the value of the second input. But my approach was a bit different - in my script I called the inputs via "input[name='date_input_1']" and "input[name='date_input_2']". However, for some reason I called the 2nd input before the 1st input and when I switched it around it seemed to fix it. By the way, this was only happening in IE. Hope this helps. On Sep 9, 10:30 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm seeing a bug using thedatepickerthat 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="http://www.google.com/jsapi";></ > script> > <script type="text/javascript"> > // Load jQuery > google.load("jquery", "1.2.6"); > google.load("jqueryui", "1.5.2"); > </script> > </head> > <body> > <div id="first"><input type="text"></div> > <div id="second"><input type="text"></div> > > <script type="text/javascript"> > google.setOnLoadCallback(init); > function init() { > $("#first > :input").datepicker({ showOn: "button", buttonImage: > "calendar.gif", buttonImageOnly: true}); > $("#second > :input").datepicker({ showOn: "button", buttonImage: > "calendar.gif", buttonImageOnly: true}); > }; > > </script> > </body> > > 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. I haven't been able to find a ticket > describing this scenario in the jQuery bug tracker. Can anyone else > reproduce this in IE6/7? Is there a fix already? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
