Skip to main content

Search and Top Navigation

#8874 closed bug (invalid)

Opened November 30, 2012 03:12PM UTC

Closed December 15, 2012 09:12AM UTC

Datepicker should prevent default when handling "prev", "next" events

Reported by: usernov30 Owned by: usernov30
Priority: minor Milestone: 1.10.0
Component: ui.datepicker Version: 1.9.1
Keywords: Cc:
Blocked by: Blocking:


I have a datepicker in an overlay above another UI component. When I click on prev/next buttons, these events propagate to this component. And I cannot catch them, since datepicker does not prevent default behaviour.

Attachments (0)
Change History (3)

Changed November 30, 2012 03:17PM UTC by scottgonzalez comment:1

owner: → usernov30
status: newpending

Preventing the default action and stopping propagation are two orthogonal concerns. I don't really understand the problem you're describing, as you're saying that the event is bubbling up to your overlay widget and at the same time you're not able to handle it because it's not reaching the widget? Please provide more information about the problem. A reduced test case in jsbin or jsFiddle would also help.

Changed November 30, 2012 03:24PM UTC by tj.vantoll comment:2

usernov30 You can use this as a starting point for a test case: Click "Fork" (in the top menu) to get started.

Changed December 15, 2012 09:12AM UTC by trac-o-bot comment:3

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!