From 5ae5866b673b4885fa9118ce3affb4b2ae296e01 Mon Sep 17 00:00:00 2001 From: annorax Date: Thu, 23 Jun 2016 17:31:40 +0300 Subject: [PATCH] Update confirm-click.coffee --- .../META-INF/modules/t5/core/confirm-click.coffee | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/confirm-click.coffee b/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/confirm-click.coffee index d8f42c720e..f77c3600cb 100644 --- a/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/confirm-click.coffee +++ b/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/confirm-click.coffee @@ -81,14 +81,10 @@ define ["jquery", "./events", "bootstrap/modal"], # Cancel the original click event return false - ($ document).on "click", "a[data-confirm-message]:not(.disabled)", (event) -> + ($ document).on "click", "a[data-confirm-message]:not(.disabled, [data-update-zone], [data-async-trigger])", (event) -> target = $ event.target - # Order of event handlers on an element is not predictable. From testing, I found this could happen. - # A bit ugly. - return if target.attr "data-update-zone" - # See note above; this replicates the default behavior of a link element that is lost because # of the window.location.href = target.attr "href"