-
Notifications
You must be signed in to change notification settings - Fork 11
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
Navigation issue, going Back #1
Comments
Actually this one is intentional, back on top nav bar is always going to root of current navigation ( collections, recently played, bookmarks - whatever you started with). To go back to previous screen use the android back button on bottom screen). Initially I have same behavior also for top back arrow that I thought it useless to have same behavior for two buttons - so top is is to jump to navigation root. |
Fair enough - but you have to press it twice to go to the root, not once?
Doesn't feel intuitive.
…On Wed., 5 Dec. 2018, 18:34 Ivan Zderadicka ***@***.*** wrote:
Actually this one is intentional, back on top nav bar is always going to
root of current navigation ( collections, recently played, bookmarks -
whatever you started with). To go back to previous screen use the android
back button on bottom screen). Initially I have same behavior also for top
back arrow that I thought it useless to have same behavior for two buttons
- so top is is to jump to navigation root.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJygR1SgGmB_wiJEkEmfaumgwNqQOivAks5u13cbgaJpZM4ZB5gz>
.
|
Maybe - I checked some Android guidelines in past - they recommend too that top back arrow should behave differently then standard back button, let's have this as an potential enhancement |
Hi there,
Just noticed a navigation issue. Can be recreated as follows:
Pressing the Android OS back button works as expected, in the same situation.
Obviously only a minor issue.
Regards,
Mike
The text was updated successfully, but these errors were encountered: