Hi

I've noticed that there are no overloaded functions for Html.EditroFor/DisplayFor, this means that the validation attributes that are generated are using the old data-val attributes instead of the new data-rule attributes. Is there anyway we could add support for this in another release?

Create MVC 5 version of jQuery.Validation.Unobtrusive.Native now it has been released. Also publish on NuGet.

Additional fields are mentioned in additional data attributes (data-rule-remote), but jQuery validation ignores them. I suspect this feature is not implemented in native jQuery validation.

Would be nice to have a list of known differences between this and Microsoft's implementation somewhere.

It appears there is no support for the EditorFor helper in the current version. Any plans to do so? I notice that the HTML generated by EditorFor produces the old MS data-val* attributes (due to UnobtrusiveJavaScriptEnabled being set to true). I've started going down the path of merging the attributes from an EditorFor(expression) and a TextBoxFor(expression, true). From what I can see, the latest version of jQuery Validation doesn't use the data-val* attributes any longer, so I'm guessing I don't need to output those at all. I'm just wondering if you've considered supporting EditorFor or if you've already found issues that wouldn't make it practical before I continue much further.

I really like the potential usefulness of jQVUN! Thanks. —Jeff

For instance, I have a model with a property named "TitleCode" and when the HTML gets rendered, I see the following:

<input name="TitleCode.TitleCode" id="TitleCode_TitleCode" type="text" 
value="Mr" data-rule-maxlength="10" 
data-msg-maxlength="The field Title must be a string with a maximum length of 10.">

The name should just be "TitleCode". My workaround is at the end.

The model property looks like

[UIHint("Text"), DisplayName("Title"), StringLength(10)]
public string TitleCode { get; set; }

I am using a EditorTemplate as follows:

@model string
@{
    var help = Html.HelpMessageFor(m => m, "help-block");
}
<div class="control-group @help.errorClass">
    @Html.LabelFor(m => m, new { @class = "control-label"})
    <div class="controls">
        @Html.TextBoxFor(m => m, true)@Html.Raw(help.message)
    </div>
</div>

I didn't fork and issue a pull request because I'd rather you look into this since I am not sure I know why this happened. I suspect it is the use of an EditorTemplate which your demos are not using and my code is.

This is my workaround in your code if this helps. This was done inside the TextBoxExtensions.cs file. It is likely that I will run into the same issue on other extensions like CheckboxFor etc.

// The foillowing code will prevent the name from being doubled up like name="TitleCode.TitleCode"
var name = metadata.PropertyName;
if (htmlHelper.ViewContext.ViewData.TemplateInfo.HtmlFieldPrefix.EndsWith(name))
    name = "";
var textBox = Mapper.GenerateHtmlWithoutMvcUnobtrusiveAttributes(() =>
    htmlHelper.TextBox(name, metadata.Model, format, attributes));
//var textBox = Mapper.GenerateHtmlWithoutMvcUnobtrusiveAttributes(() =>
//    htmlHelper.TextBox(metadata.PropertyName, metadata.Model, format, attributes));

I like your project, nicely done.

On the home page of JVun demo site, the Advanced Dynamic Demo URL points to "http://localhost:57612/AdvancedDemo/Dynamic".

(As displayed on the Page)

1. Dynamically created form elements are parsed automatically. jquery.validate.unobtrusive.js does not support this whilst jQuery Validation does.
   See a demo

I also don't see that page on github under: jQuery.Validation.Unobtrusive.Native/jVUNDemo/Views/AdvancedDemo/

Migrate Globalize example to 1.x

any plans to include EnumDropDownListFor?

Not sure if it's a bug with Unobtrusive Native, but I'd like to solicit thoughts.

Repro steps are fairly simple:

1. open the Advanced Demos/Tooltip demo (https://johnnyreilly.github.io/jQuery.Validation.Unobtrusive.Native/AdvancedDemo/Tooltip.html)
2. set focus on the first input field ("A number must be entered:")
3. hit Enter

The input fields turn red (which is good as they're invalid), the "The TextBox field is required." popover error message appears for a moment then immediately disappears.

From what I can tell, the 'show' event gets fired by the tooltip, but 'shown', 'hide' or 'hidden' do not.

I keep in investigating, if I get to any results, will post a follow-up comment. Thoughts are welcome.

I intend to do this prior to tackling migrating jQuery Validation Globalize to Globalize 1.x. (and I publish jQuery Validation Globalize using Bower)

johnnyreilly/jquery-validation-globalize#8

Hey guys, i had to recompile the DLL to change the namespace of the DropDownListFor

For some reason it is in the wrong class.

in the original DLL it is in DropDownListExtensions

My framework is trying to find it in the SelectExtensions instead.

And place it into the System.Web.Mvc.Html namespace.

It works for me now that i recompiled it.

I recently gave a try to this plugin, unfortunately it doesn't seem to perform client side validation on IE8.

To be fair, that was the reason why I took a look a this plugin because it was not working on my implementation.

Reproducing this problem is fairly easy.

On IE8 ( no compatibility mode or emulation mode)
Go to: http://jqueryvalidationunobtrusivenative.azurewebsites.net/Demo/Required
Press Submit.

A post is done and no feedback is provided.

I do realise this is a fairly tricky question, but I was looking for someone who could either shed some light or at least share known possible workarounds.

On top of that IE8 flag the following errors:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Timestamp: Wed, 5 Mar 2014 16:51:07 UTC

Message: Object doesn't support this property or method
Line: 1
Char: 14863
Code: 0
URI: http://jqueryvalidationunobtrusivenative.azurewebsites.net/bundles/jquery?v=OCFAn1NcaUrZ5VLi0Kt8lefDjHOF7mvtdw-2FUpZjJ01

Message: Bootstrap requires jQuery
Line: 1
Char: 31
Code: 0
URI: http://jqueryvalidationunobtrusivenative.azurewebsites.net/bundles/bootstrap?v=TrsnDoe6JguD6Lw3KbE7sMj0JMocLZEq5ursbRw7N3s1

Message: 'jQuery' is undefined
Line: 1
Char: 1
Code: 0
URI: http://jqueryvalidationunobtrusivenative.azurewebsites.net/bundles/jquery-validation?v=v2z4Z8qXYF6JsuzzQtx0LtcGD7Um7k1RcQLNLYyA-NE1

Message: Object expected
Line: 305
Char: 9
Code: 0
URI: http://jqueryvalidationunobtrusivenative.azurewebsites.net/Demo/Required

I am using Jquery unobtrusive validations with mvc and i have a model with field
int? MinSalary{get;set;}

the validations work fine in mozilla and ie but fail in chrome when i add the Non interger input in the text box

    @Html.LabelFor(m => m.MinSalary)
                            @Html.TextBoxFor(m => m.MinSalary, new {  @class = "form-control", type = "number", min = "0",  })
                            @Html.ValidationMessageFor(m => m.MinSalary)

the validation also works fine with type="text" but shouldnt it also work otherwise.

Hi
I don't know if it's a normal behavior but validation doesn't work when you use a multi level models like this

public class MainModel
{
      public Model1 model1 { get; set; }
      public Model2 model2 { get; set; }
}

All validations fail even if the model is valid.

Luckily I have only validation in 1 model so I changed the code for

public class Model1
{
      public Model2 model2 { get; set; } // no validation in this one

      // All the properties with validation directly here
      ...
 }

I don't know if there's a reason for this. If not I think it could be a nice improvement.

Thank you
Marc

I've noticed that both the regular MVC implementation and your "Native" implementation do not automatically write out the constraint attributes that are native to HTML5.

Things like:

• required
• maxlength
• max
• min
• etc.

Doesn't jQuery Validation support these HTML5 attributes natively now? In case something goes wrong with the script, this would still allow you to provide a validation through the regular browser-native validation constraints.

It feels wrong to rely only on data-attributes for things that are actually supported and built into HTML5.

Validation fail if a MVC model property name is Number.

Your library doesn't support regex validation (RegularExpressionAttribute). Please add it.
Microsoft jQuery Unobtrusive Validation supports it.

I don't know what would have caused this, but we just noticed this during our development today. I noticed that the HTML output is adding the [data-rule-required] attribute, despite having no [Required] attribute on our model.

We only want our booleans to be required if the [Required] attribute is added to the view model. Amy I missing something?

We're using jQuery.Validation.Unobtrusive.Native.MVC5 (1.3.0) and jquery.validate.js (v1.15.0).
Here's our code.

public class SomeViewModel
{
    public bool Terms { get; set; }
}

@model SomeViewModel

@using (Html.BeginForm())
{
    @Html.CheckBoxFor(m => m.Terms, true)
    <button type="submit" class="btn btn-primary">Submit</button>
}

Am I missing something?

The primary reference "X" could not be resolved because it was built against the "Y" framework. This is a higher version than the currently targeted framework "Z".

I use .NET Framework 4.0 and MVC 3, but dll-file compiled for "4.5".

Are you might to compile nuget-package for other versions of .NET Framework?

Hi, firstly thanks for sharing the great project.

Having a small issue. When generating client side attributes for an integer field. The data-rule generated is for "number" when instead is should be a "digit". This means client side validation does not occur when an invalid decimal value is entered.

Thanks again.
Matt

Hi. FIrst up thanks for this lib.

I was curious about the expected behaviour of bools/checkboxes. Note that using the example below, built-in unobtrusive validation produces no validation message (default(bool) is valid) for the checkbox.

This library produces a (required) validation message.

ModelState errors collection for 'Obsolete' is empty in both cases.

I think the default behaviour should be preserved, thoughts?

View:

@model WebApplication1.Controllers.TestViewModel
@using (Html.BeginForm())
{
    <div class="form-group">
        @Html.CheckBoxFor(p => p.Obsolete, true)
        @Html.ValidationMessageFor(p => p.Obsolete)

        @Html.TextBoxFor(p => p.Test, true)
        @Html.ValidationMessageFor(p => p.Test)
    </div>

    <input type="submit" value="Submit" />
}

@using (Html.BeginForm())
{
    <div class="form-group">
        @Html.CheckBoxFor(p => p.Obsolete)
        @Html.ValidationMessageFor(p => p.Obsolete)

        @Html.TextBoxFor(p => p.Test)
        @Html.ValidationMessageFor(p => p.Test)
    </div>

    <input type="submit" value="Submit" />
}
@section scripts {
    @Scripts.Render("~/bundles/jqueryval")
<script>
    $('form:eq(0)').validate();
    </script>
}

Controller:

public ActionResult Index()
        {
            var viewModel = new TestViewModel(); 
            return View(viewModel);
        }

        [HttpPost]
        public ActionResult Index(TestViewModel viewModel)
        {
            if (ModelState.IsValid)
            {
                return View();
            }
            return View(viewModel);
        }

ViewModel

public class TestViewModel
    {
        public bool Obsolete { get; set; }

        [Required]
        public string Test { get; set; }
    }

Hi Guys,

Awesome project. (MVC5 version)

Not sure if this is a bug for feature. I'm getting lots of ""System.Collections.Generic.Dictionary`2+ValueCollection[System.String,System.Object" and a hidden input as well

Using:
@Html.CheckBoxFor(x => x.Accounttype1,true)

Where:
[Display(Name = "TFSA")]
[Required(ErrorMessage = "What type of account or accounts would you like to open?")]
public bool Accounttype1 { get; set; }

I get this html:

 <input type="checkbox" value="true" name="Accounttype1" id="Accounttype1" values="System.Collections.Generic.Dictionary`2+ValueCollection[System.String,System.Object]" keys="System.Collections.Generic.Dictionary`2+KeyCollection[System.String,System.Object]" count="2">
 <input type="hidden" value="false" name="Accounttype1">

Your project does not support ValidationMessage and ValidationSummary, I think you should document that. While nothing stops you from using ValidationMessage and ValidationSummary, you cannot share the same element to display server and client messages, hide the server message when validating, show messages in the summary instead by each individual control, etc. These features are exclusive to the unobtrusive library.

Is this going to be updated to use ASP.NET Core.

I could have a go if you can't.