I am trying to implement optional client side validation using
- ASP.NET MVC 4,
- unobtrusive jQuery validation,
- unobtrusive ajax
This works fine
Following pictures show what I mean with optional client side validation: The only one field on my form is expected to contain email, so there is an email validator attached to it.
Now we click on save. Because our text "name@doamin" is not a valid email the validation summary gets displayed. Together with validation summary we are unhiding "Save anyway" button.
This second button is a normal submit button just having class="cancel"
. This instructs jQuery.validate.js
script to skip validation when submitting using this button.
Here is the code snippet of the view:
@using (Html.BeginForm())
{
<div>
<input data-val="true" data-val-email="Uups!" name="emailfield" />
<span class="field-validation-valid" data-valmsg-for="emailfield" data-valmsg-replace="false">*</span>
</div>
<input type="submit" value="Save" />
@Html.ValidationSummary(false, "Still errors:")
<div class="validation-summary-valid" data-valmsg-summary="true">
<input type="submit" value="Save anyway" class="cancel" />
</div>
}
These all works fine.
The problem
The second submit button - "Save anyway" stops working as expected if I switch over to Ajax form. It just behaves like the the normal one and prevents submit until validation succeeds.
Here is the code snippet of the "ajaxified" view:
@using (Ajax.BeginForm("Edit", new { id = "0" },
new AjaxOptions
{
HttpMethod = "POST",
InsertionMode = InsertionMode.Replace,
UpdateTargetId = "ajaxSection",
}))
{
<div>
<input data-val="true" data-val-email="Uups!" name="emailfield" />
<span class="field-validation-valid" data-valmsg-for="emailfield" data-valmsg-replace="false">*</span>
</div>
<input type="submit" value="Save" />
@Html.ValidationSummary(false, "Still errors:")
<div class="validation-summary-valid" data-valmsg-summary="true">
<input type="submit" value="Save anyway" class="cancel" name="saveAnyway" />
</div>
}
I have debugged jQuery.validation.js
to find out what is the difference, but failed.
Qustion
Any ideas to fix or workaround the problem and let the ajax form behave as intended are welcome.
Addendum
To have a client side validation is an absolute must. Server side validation is not an option. Aside from higher traffic (this sample is a simplification - the real form contains much more fields) and latency, there is one thing which server side validation would not do: client side validators highlight erroneous fields on lost focus. It means you have a feedback as soon as you tab to the next field.
if Unobtrusive validation is not required, disable it and do all your checking on the server side.
You could check value of Submit button on the server side and proceed based on that:
add
name
attribute to both of your submit inputs:Update your action to take
string btnSubmit
. You may just put it in your model if you have one.UPDATE
I understand that client validation simplifies the job, but if you cannot figure out what is wrong with Ajax (i'm not familiar with it's behavior when class="cancel" is slapped on an input), you could write a script that would validate an input on the un-focus on the server side:
Now you need to create an action that will do the validation of an input:
It's a bit of a hassle, but as I said, could work if you do not figure out client validation.
UPDATE
Don't know why I didn't think of this first... rather than relying on
class="cancel"
you could do something like this:Give your "anyway" submit input Id:
Then have a script like this:
I haven't tested this, but in theory, this should submit form without validating it. You probably still will need server side validation as I showed in my very first example.
FINALLY I figured out a solution that in itself is unobtrusive
Note: If at first try it appears that this isn't working - make sure you're not roundtripping to the server and refreshing the page with errors. You'll have to bypass validation on the server side by some other means - this just allows the form to be submitted without having to mess around adding
.ignore
attributes to everything in your form.(you may need to add
button
to the selector if you're using buttons)That's a known limitation of Microsoft's unobtrusive ajax script. You could modify it to fix the bug. So inside the
jquery.unobtrusive-ajax.js
script replace the following on line 144:with:
In addition we are passing the class name to the handler so that it can decide whether it should trigger client side validation or not. Currently it always triggers validation no matter which button was clicked. And now on line 154 we modify the following test:
with:
so that client side validation is no longer triggered if a submit button with class name cancel was used to submit the form. Another possibility is to scrape the
jquery.unobtrusive-ajax.js
script and replace yourAjax.BeginForm
with a standardHtml.BeginForm
that you could unobtrusively AJAXify using plain old jQuery.