@Shadow Wizard Well, I just sort of operate on the "ampersands always escaped" assumption in raw HTML.But I added a sample that the W3C validator chokes on.Parsley comes with various error messages for its built-in validators.
I'm not sure it would fit the definition of an ambiguous ampersand, as that suggests it's for when an entity ends with a semicolon but can't be identified as one of these...
It helps you provide your users with feedback on their form submission before sending it to your server.
Please take 5 minutes of your time to have a quick glance at it, and at least understand the architecture (Parsley, Parsley Form, Parsley Field, Parsley Validator, Parsley UI, Utils, Pub/Sub..), it will heavily ease the lecture below.
Your custom validator must specify at least one of these.
You can specify what kind of requirement parameter your custom validator is expecting: as second and third arguments (the first one being the value(s) to validate).