Native browser validations on submit is a good first step, at least they dont' have to submit the form then :)
I would say try using checkValidity or reportValidity whenever the password field changes, that will run the browser's own validation again (before submit). That would be nice, but I suspect that in some browsers it might interfere with the user typing. If that happens, then I would suggest displaying our own message right next to the input field, maybe using the "tooltip" javascript widget so it can point right at the field. --- ** [tickets:#7459] Show password requirements on forms** **Status:** open **Milestone:** unreleased **Created:** Wed Jun 11, 2014 03:46 PM UTC by Dave Brondsema **Last Updated:** Thu Oct 18, 2018 04:49 PM UTC **Owner:** nobody It would be helpful to show password requirements (aka min # of chars) on the password change form. And account creation. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
