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

[usernov30]

Hello,

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.

[Scott González]

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.

[tj.vantoll]

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

[trac-o-bot]

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!