Hi,
[sorry it took me so long to come back to this..]
anonym wrote (13 May 2014 09:45:43 GMT) :
> 12/05/14 17:41, intrigeri wrote:
>> The rest of the suggested changes make sense to me. The t-p-s UI is
>> way nicer, with a nice little warning dynamically updated as long as
>> entered password confirmation does not match. And I stole it from
>> GNOME Disks, iirc, which makes the UX more consistent.
> Note that we have some form of "dynamic behaviour" for the error (from
> commit c96200f [1]) but that it's not exactly the same as in t-p-s; the
> mis-match error is only shown after trying to login when the fields
> differ, and the error is immediately removed when one of the fields
> change.
That's not what I call "dynamic": the idea behind this ticket was
indeed to provide feedback *before* clicking on the "Log in" button,
just like many forms on the web these days validate input with JS
as they're being filled.
> IMHO this is a better behaviour than always showing it, at least
> in the Greeter's context where we do not have a default error to show
> (like "passphrase can't be empty" in t-p-s).
I'm curious why :)
> Given that the semantics of the fields are pretty different in the
> Greeter compared to in t-p-s, please provide a detailed description of
> how you think the Greeter should be changed in case you still think it's
> desirable.
What I had in mind is:
a. I click "More options"
b. I see the more options screen
c. I type an admin password
d. I type it again in the "Confirm" field
e. while I'm typing it, and then while I'm wondering whether I want
to select other options, I'm told if I didn't type the same
password twice
I'll add this discussion's conclusions to the ticket once we
reach any.
Cheers!
--
intrigeri
