Remote validation doesn't respect data-trigger
See original GitHub issueIt would seem that the remote validation method doesn’t accept the various data-trigger options. It starts with focusout
, and when you focus again, it switches to keyup
. Keyup causes too many server requests, so i’m hoping to get it to stay on focusout
, blur
, or something more-or-less equivalent.
Issue Analytics
- State:
- Created 11 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Remote validation doesn't pass data to action - Stack Overflow
Try using you model as the parameter. So that it could bind the value to it. public JsonResult ActionName(MyModel model) { //..
Read more >Remote validation is not raised when a value is empty
Hi! The remote validation is not called when the value is null (see the attached video) . It's important to call validation even...
Read more >Razor Pages - Unobtrusive Validation Issue - Telerik
I have extended the kendo validation to include remote validation to check if a field name exists in the database already, that all...
Read more >Trigger Overview - MariaDB Knowledge Base
A trigger, as its name suggests, is a set of statements that run, or are triggered, when an event occurs on a table....
Read more >Using Triggers - Oracle Help Center
Trigger names must be unique with respect to other triggers in the same schema. ... then Oracle cannot validate the statement accessing the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I tried parsley 2.0 and it works ok on change but it doesn’t fire remote validation on form submit even if field has been validated previously.
Hi,
Parsley 2.0 is out. I do not support anymore 1.x versions and related issues here.
Please, see if 2.0 fix your concern. If not, feel free to ask for help on StackOverflow, there is a #parsley.js tag.
Thanks