<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;">The problem I see is that people don’t read these messages. They assume that it is an error or something.<div><br></div><div>I think the text above (some different from a feedback message) is more effective, and the extra field (username) helps on the differentiation. It could be plain text instead of an input.</div><div><br></div><div>I don’t believe this solution will solve the problem.</div><div><br></div><div>Gabriel </div><div><br></div><div><br><div><div>On May 21, 2014, at 4:37 AM, Stian Thorgersen <<a href="mailto:stian@redhat.com">stian@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I added it the way you said, and to me it doesn't stand out at all. How about moving the notification bubble we already have to be in-line with the form? That would also make all other notifications, such as invalid username/password stand out more as well. See attached screenshot for how that would look like.<br><br>Adding a disabled input field for username doesn't make sense at all to me. An input field is not informative, it's an input field and hence something users expect to fill in.<br><br>----- Original Message -----<br><blockquote type="cite">From: "Gabriel Cardoso" <<a href="mailto:gcardoso@redhat.com">gcardoso@redhat.com</a>><br>To: "Stian Thorgersen" <<a href="mailto:stian@redhat.com">stian@redhat.com</a>><br>Cc: "Bill Burke" <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>, <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>Sent: Tuesday, 20 May, 2014 7:11:20 PM<br>Subject: Re: [keycloak-dev] Issues with the first login flow<br><br><blockquote type="cite">He's not logged-in, those are actions that the user are required to do<br>prior to be logged-in. The user will however have to identify himself with<br>username/password (and totp if configured) prior to being permitted to do<br>those actions. The actions a user can be asked to do as part of a login is<br>not just limited to updating the password. These can include:<br><br>* Configure TOTO<br>* Update password<br>* Verify email<br>* Update profile<br><br>And, possible more to come in the future.<br></blockquote><br>Thanks for the clarification.<br><br><blockquote type="cite">Text above we already have in a notification thing, but I don't have a<br>problem with moving that above the form. The username input field doesn't<br>make sense at all, as the user is not able to change that at this stage.<br></blockquote><br>Cool, so please put the text inside a <p class=“form-info”></p>.<br><br>The username field is to differentiate more this page from the login page (3<br>fields are different than 2 :) I don’t see it as a problem, it is<br>informative and the user can’t change it (no danger). So now it is up to<br>you.<br><br>Thanks,<br>Gabriel<br><br><blockquote type="cite"><br><blockquote type="cite"><br>Gabriel<br><br>---<br>Gabriel Cardoso<br>User Experience Designer @ Red Hat<br></blockquote></blockquote><br>---<br>Gabriel Cardoso<br>User Experience Designer @ Red Hat<br><br></blockquote><span><login-notification.png></span></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></div></body></html>