<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Attached is how we are dealing with required fields on LiveOak. If the user doesn’t fill in some required field, it is not possible to Save.</div><div><br></div><div><img apple-inline="yes" id="AC4016E1-22C7-42A3-A50A-2EACD5FD238B" height="319" width="578" apple-width="yes" apple-height="yes" src="cid:0B43CB43-B18F-48E8-A75A-C99EFBA28290"></div><div><br></div><div>And for smaller resolutions:</div><div><br></div><div><img apple-inline="yes" id="B910FEC4-ADC7-48A0-9776-BA31EE405C97" height="160" width="399" apple-width="yes" apple-height="yes" src="cid:2E505D4A-1107-4FAC-97CA-25BF3197C166"></div><div><br></div><div>Regarding the password validation, there are some advocating that this interaction can be improved by providing a way for the user to see the password rather than asking him to type it twice [1]. </div><div><br></div><div>We implemented this on LiveOak by including an eye icon in the input, that reveals the password. </div><div><br></div><div><img apple-inline="yes" id="88F03B42-091D-4133-97B6-5B7E4CA63800" height="104" width="377" apple-width="yes" apple-height="yes" src="cid:8C732D60-154A-4945-9D4F-C71E82566E70"></div><div><br></div><div>Gabriel</div><div><br></div><br><div><div>On Jul 3, 2014, at 10:57 AM, Andreas Nilsson <<a href="mailto:anilsson@redhat.com">anilsson@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 07/03/2014 03:42 PM, Robb Hamilton wrote:<br><blockquote type="cite"><br>there was another request this week for rules regarding form validation. specifically, how to handle the validation of password inputs when creating a new password where the password has to be input twice (does this happen client-side, server-side? what messaging appears and when? etc.).<br></blockquote><br>We're currently working on solving this in Cockpit here: <a href="https://github.com/cockpit-project/cockpit/issues/739">https://github.com/cockpit-project/cockpit/issues/739</a> and the pull request <a href="https://github.com/cockpit-project/cockpit/pull/809">https://github.com/cockpit-project/cockpit/pull/809</a> but it would be great to have this code live in Patternfly instead of locally in our cockpit-accounts.js<br>So here is the current behaviour:<br>* On error, both fields turns red, since the error refers to both fields and the typo of your regular password could have happened in the first field.<br>* The password is getting checked while you're typing. If the secret password is "hacker" the fields will turn red already at the "o" if typing "hackor" in the second field. This catches typos right away.<br>* There is a timer of 2 seconds for the second field so it can catch things like a missing last "r" in the case of the "hacker" password is just "hacke"<br>* There is certainly room to improve the logic above, but I feel it covers at least the basic cases for now.<br>* There is still a tiny issue in that if you focus the first field with the mouse, and then use tab to jump to the second field and do an error, the first field will remain red due to the blue hover effect on the first field.<br>- Andreas<br><br>_______________________________________________<br>Patternfly mailing list<br><a href="mailto:Patternfly@redhat.com">Patternfly@redhat.com</a><br>https://www.redhat.com/mailman/listinfo/patternfly<br></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>---</div><div>Gabriel Cardoso</div><div>User Experience Designer @ Red Hat</div></div>
</div>
<br></body></html>