Form validation: email input type and the multiple attribute

[RobJohnston]

HTML5 has a multiple attribute that can be specified for e-mail addresses as well as files. For e-mail, it would be a set of comma-separated strings, each of which is a valid email address.

When applying the multiple attribute to the existing form validation example, more than one e-mail address will not validate.

I do have a work-around, but it involves changing the input type from "email" to "text". Any thoughts on this? Is there a better way?

<div class="wb-frmvld">
    <form action="#" method="get" id="validation-example">
        ...
        <div class="form-group">
            <label for="email1"><span class="field-name">Email address</span> (yourname@domain.com)</label>
            <input class="form-control multiemail" id="email1" name="email1" type="text" />
        </div>
...
    <script type="text/javascript">
        wb.doc.on("wb-ready.wb", function (event) {
          jQuery.validator.addMethod("multiemail", function (value, element) {
                    if (this.optional(element)) {
                        return true;
                    }
                    var emails = value.split(','),
                        valid = true;
                    for (var i in emails) {
                        value = emails[i];
                        valid = valid && jQuery.validator.methods.email.call(this, value, element);
                    }
                    return valid;
                }, jQuery.validator.messages.email);
        });
    </script>

[LaurentGoderre]

Maybe post an issue to jQuery Validation?

[RobJohnston]

I considered that, but jQuery Validation doesn't use the type="email" either, not even for a single e-mail address, so I assumed it was a WET thing. See http://jqueryvalidation.org/email-method/

Ideally, would just want to enter this:

<input class="form-control" id="email1" name="email1" type="email" multiple />

[RobJohnston]

Let's slap an "upstream" label on this. See jquery-validation/jquery-validation#1722. I don't know when I'll get to it.