#3662 closed feature (notabug)
Cancel event bubbling from datepicker
| Reported by: | leemhenson | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | ui.datepicker | Version: | 1.6rc2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Patch attached which adds support for a cancelBubbling option, as described in this post:
http://groups.google.com/group/jquery-ui/browse_thread/thread/dad394c24354f756
Essentially it allows the user to stop onclick/onchange events escaping the datepicker, as the rebuild of the datepicker html that occurs before the bubbling means that the event.target points at a node which is no longer in the dom.
Attachments (1)
Change History (4)
Changed 14 years ago by
| Attachment: | datepicker.patch added |
|---|
comment:1 Changed 14 years ago by
comment:2 Changed 13 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I think this is now the wrong approach to solve my problem. Since the w3c spec says the path to doc root is calculated and fixed at the point at which the event is raised, it is reasonable for the datepicker to do what it's doing and cause the situation detailed in my post. The other framework in play (javascriptmvc) has been updated to handle disconnected trees of nodes.