From 6239e950d00b79265af9095a7f817ed5a8b98203 Mon Sep 17 00:00:00 2001 From: James Wagoner Date: Mon, 10 Feb 2014 00:17:08 -0800 Subject: [PATCH] Update ngEventDirs.js The documentation states only the "action" attribute triggers this, which is incorrect. When using the attribute "data-action" (as for AJAX control, attempting to bypass the "action" attribute but still make it obvious what its for), Angular thinks this is also classified as "action" and continues with the page submission. --- src/ng/directive/ngEventDirs.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/ng/directive/ngEventDirs.js b/src/ng/directive/ngEventDirs.js index f63d3ca1e7bf..7289580e147c 100644 --- a/src/ng/directive/ngEventDirs.js +++ b/src/ng/directive/ngEventDirs.js @@ -298,8 +298,8 @@ forEach( * Enables binding angular expressions to onsubmit events. * * Additionally it prevents the default action (which for form means sending the request to the - * server and reloading the current page) **but only if the form does not contain an `action` - * attribute**. + * server and reloading the current page) **but only if the form does not contain `action` or `data-action` + * attributes**. * * @element form * @priority 0