Skip to main content

Search and Top Navigation

#6987 closed bug (invalid)

Opened February 14, 2011 03:26PM UTC

Closed November 03, 2012 08:52AM UTC

Datepicker incorrectly shown during alt tab

Reported by: jcdekker Owned by: jcdekker
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8.9
Keywords: Cc:
Blocked by: Blocking:
Description

When you change the value of an input (that has a date picker) in the blur event, the date picker is suddenly shown and shown at an incorrect position when you put the focus back on the input using the alt tab key combination.

This happens in both internet explorer as firefox (didn't test other browsers).

This bug is introduced in version 1.8.7 but still exists in version 1.8.9.

In version 1.8.6. it runs as expected.

The following shows the code:

$('input.date')
 .datepicker(
      { dateFormat: 'dd/mm/yy', showOn: 'button', 
        buttonImage: 'Images/calendar.gif', buttonImageOnly: true 
  })
 .blur(function(event) {
   var target = formGetJavascriptEventTarget(event)
   jqTarget = $(target);
   jqTarget.val('1/1/2000');
});
Attachments (0)
Change History (4)

Changed February 14, 2011 03:47PM UTC by jcdekker comment:1

I'm sorry, instead of alt tab i mean shift tab.

Changed October 11, 2012 02:43PM UTC by scottgonzalez comment:2

milestone: 1.9.01.11.0

Changed October 19, 2012 06:13PM UTC by mikesherov comment:3

owner: → jcdekker
status: newpending

Thanks for taking the time to contribute to the jQuery UI project! I couldn't reproduce the issue using the latest versions of jQuery and jQuery UI: http://jsfiddle.net/eB4QT/2/

Please let me know if you have any questions, and if there is still a bug, please respond and let me know!

Changed November 03, 2012 08:52AM UTC by trac-o-bot comment:4

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!