See attached image; it's not obvious here that there is an item that's scrolled off the left hand side (my user) or how to get back to it; if this thing is going to scroll it needs a scrollbar to inform the user that they have stuff to scroll back to (or also given the width it really doesn't need to scroll it off). Reproducible: Always Steps to Reproduce: 1. ctrl-alt-l to lock screen 2. Click change-session Actual Results: The users own icon scrolls off to the left, without any indication to the user of how to get it back, or indeed that it was there Expected Results: Something to indicate that the user can scroll or select an icon to get back to their users icon
Created attachment 88579 [details] Screen capture of lockscreen
VDG?
I just wanted to report the same problem. I took me five mins to figure it out and find the hidden icon with my username.
I don't think a scrollbar is really necessary here. While it is a well known UI element it would also break the balance of the UI unnecessarily. My preferred solution would be to turn the dialogue into a carousel UI i.e. the currently hidden item to the left hand sight would re-appear on the right hand side. I think we should go for this first and then see how it works out. If this still doesn't suffice we should also add vertically centred arrow-buttons to indicate that one can scroll to the left and right. The carousel should, in theory, work quite well though.
I think a carousel would work but only if it was obvious; i.e. if you had something like the left/right hand ones being faded /partly obscured to show they were going 'off the edge' - I don't think it would work without something like this, or as you suggest some arrows.
My impression was that his is already the case (I haven't used it in action yet), as the icon gets smaller and more transparent. But I agree, if that does not work out we need to tweak it in other ways, too.
@Philipp that's the main problem; we cut off (deliberately) exactly after one icon to the left of the centre, and there's no border anywhere to signify it's the edge.
Ok, so here's my proposal: Make this view a carousel and add buttons, along with one of these fancy "scroll bars" (no idea how they are called, really) below the selected option. Quick and dirty mockup incoming.
Created attachment 90136 [details] Carousel proposal
Comment on attachment 90136 [details] Carousel proposal Yeh that should work
and what to the dots do/represent?
Yeh I wondered that; you can't really make them be one per slides-worth; you could have hundreds of users (on a company system with ldap/nis); you could regard them as two end stops and an 'in the middle'.
@David Those resemble the number of entries. I assumed that this screen has 3, so 3 dots are displayed. If there are more entries then there are more dots. The dots should be centred, until they come close the the arrow-buttons. When this happens the whole area, buttons+ dots would expand in width. In this mockup I assumed that the most common setup has no more than a couple of entries/sessions/users. @Dave They resemble the entries. One dot + the distance to the next are ~16px here. The entries in the mockup + the clock take up roughly 550px. That's space for almost 34 different entries/users. I will be as bold to suggest that this is a rather uncommon setup. Big companies will most likely have an option to connect remotely, where one enters the account name and credentials, instead of displaying all the possible accounts.
Be careful about the company assumption; it depends on the way NIS interracts with the code that gets the user list; I've not got a NIS setup here, but it's been a common problem on previous login managers for them to have problems in a NIS environment with lots of users.
@Dave Fair enough, even though I still find it very nonsensical to have to scroll through a list of more than a dozen different users. But that's the problem of the company I guess. Anyway, the dots are a mere suggestion. We do not need them. However, if we do not go for the dots, I will probably have to find another place for the arrow-buttons, because they area looks a bit too empty without them, for my taste.
@Philipp: No! That's not the companys problems, it's the UI designer - don't just assume the login screen is just used on a 1 user desktop/laptop! Most login screens used to have the icon AND a text entry so that you could type the username rather than having to find it; it's a standard Linux setup on a networked installation.
I am confused. How would my mock-up inhibit this behaviour? the mock-up solely deals with the problem that it is not obvious for users that there might be entries hidden. The setup you describe is sensible, but that's not the problem the mock-up is dealing with. If you want such a remote login feature implemented then please fill a separate bug report.
Yeh agreed it is a separate problem; I think this all just stemmed from the what do the row of dots mean. Your fix for the scroll problem is much better than what we have.
I don't think a scrollbar fits the design here. The carousel idea is an interesting one. However, I personally like to avoid a carousel list navigation just because I think it can confuse the spatial model of where things are located when the begin and end of a list is not defined. I'd suggest, a simple visual indication that there is something beyond what is visible: a vertically-centered dot, in the foreground color, on the side where an item is available beyond what's currently visible.
Andrew: Can you suggest any other app that uses that 'dot' based design to indicate that? I don't think we should invent new GUI elements here. (I guess this also needs to fit in with accessibility stuff, but I don't know anything about that).
David: Well I'm not sure we have many other apps to appeal to that uses this style of horizontal scrolling list. The closest thing I seen are image carousels, similar to what has already been suggested here. I have shared my concerns about a carousel design. I'm certainly open to other ideas. Mine was simply a suggestion.
*** Bug 344111 has been marked as a duplicate of this bug. ***
This isn't an issue with the current or 5.13 lock screen designs.