Search and Top Navigation
#8652 closed bug (fixed)
Opened October 11, 2012 04:55AM UTC
Closed October 23, 2012 06:08PM UTC
Widget: Destroy only when element is the actual target
| Reported by: | marcandre | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.9.1 |
| Component: | ui.widget | Version: | 1.9.0 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
If ever a 'remove' event was not triggered on the actual widget but on a child element and is just bubbling up, then nothing should be done.
Use case: I use a 'remove' event (with bubbling) in my app and without this patch it interferes if the element I trigger it on is contained in a jQuery-ui widget.
Testcase from stackoverflow question: http://jsfiddle.net/yWg8v/7/
Attachments (0)
Change History (3)
Changed October 15, 2012 03:27PM UTC by comment:1
| description: | If ever a 'remove' event was not triggered on the actual widget but on a child and is just bubbling up, then nothing should be done. \ \ Use case: I use a 'remove' event (with bubbling) in my app and without this patch it interferes if the element I trigger it on is contained in a jQuery-ui widget. \ \ http://stackoverflow.com/questions/12584732/how-come-sortable-area-freezes-if-a-remove-event-is-triggered → If ever a 'remove' event was not triggered on the actual widget but on a child element and is just bubbling up, then nothing should be done. \ \ Use case: I use a 'remove' event (with bubbling) in my app and without this patch it interferes if the element I trigger it on is contained in a jQuery-ui widget. \ \ http://stackoverflow.com/questions/12584732/how-come-sortable-area-freezes-if-a-remove-event-is-triggered \ Testcase from stackoverflow question: http://jsfiddle.net/yWg8v/7/ |
|---|---|
| status: | new → open |