Skip to main content

Search and Top Navigation

#7266 closed bug (duplicate)

Opened April 18, 2011 09:23AM UTC

Closed January 27, 2013 02:17AM UTC

datepicker taborder - focus problem internet explorer

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

I've got a test case in jsFiddle to show the problem: http://jsfiddle.net/lankarden/9FtnW/

A default datepicker will break the taborder when the date is selected via the popup, in the test case, hitting the tab key after selecting the date with the mouse, will result in the first field of the form getting the focus.

I found a fix for this problem, but it creates another one: after selecting the date via the popup with the mouse, internet explorer (I use IE8, but i think the problem occurs in all versions) presents the popup again.

Attachments (0)
Change History (5)

Changed April 20, 2011 07:02PM UTC by cmoschini comment:1

This also occurs in Chrome 10/Windows and FF3.5/Windows - I suspect this bug is not browser-specific and instead just a general bug in the code.

Changed May 15, 2011 05:56AM UTC by fracmak comment:2

There's an if statement in there preventing the focus from being reestablished, probably to fix the issue you're describing with IE. There's a weird hack in the code to prevent the dialog from reappearing when a focus event happens and they don't mean it to trigger the dialog, except it fails in IE because IE queues up the focus event until after the current execution is done, so the hack doesn't work. Again, the current broken if statement is bypassing it. This essentually is a chicken and an egg problem which requires more thought before a solution is provided.

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

milestone: 1.9.01.11.0

Changed October 19, 2012 06:45PM UTC by mikesherov comment:4

status: newopen

Changed January 27, 2013 02:17AM UTC by tj.vantoll comment:5

resolution: → duplicate
status: openclosed

Duplicate of #7765.The core issue here is that focus is not being placed back in the input.