-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot quickly navigate to end of list #36
Comments
Hi @bkjohnson , the ilia UI has a filter box followed by the list of entries. When at the top element, when pressing up, this causes focus to return to the filter box. I think it would be a UX regression to change this behavior. what would your ideal experience be?
|
Hi @kgilmer, I say 1 and 2 both would be nice
Note: page up and down keys only work if you are on the list. When you open it first you need to go one down before you can use the page down key |
I was unable to get
This has been fixed however. In 2.2 you can directly hit |
Sorry for the delayed response. To answer your earlier question, I think an ideal experience for me would be a specific key to navigate to the end and when I dismiss a notification, move focus to the one immediately above rather than sending me all the way back to the top of the list. My use case involves sometimes leaving notifications in the ilia dialog even though I've "read" them so that they act as reminders until I'm actually ready to dismiss them. So if I get some new notifications when I already have a few stacked up I have to go all the way down to the bottom of the list ( |
Thanks @bkjohnson , your workflow is perfectly clear. I'll keep this in mind. |
With rofication, I could open my notifications and use the up arrow to quickly go to the end of the list to see my most recent notifications. This doesn't seem possible with ilia. If I want to get to the most recent notifications I might have to press down a dozen times or more.
Is this functionality that is planned to be added?
The text was updated successfully, but these errors were encountered: