-
Notifications
You must be signed in to change notification settings - Fork 223
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
Don't go into repository page after selecting issue, make title go to repository instead #1085
Comments
I do not understand the problem at this moment. Is your problem the behavioral difference of the back button (of device or in navigation bar) and the back button in the title bar? If so, that difference is both intended and suggested by Google's guidelines: the nav bar back button should do 'temporal' back navigation, while the title bar back button should do 'hierarchical' back navigation. |
@maniac103 I assume you misunderstood. It's ok, I'll brake it down.
Instead of going through all that, after pressing back, I would prefer to stay on my issue list, not go into the "Project's" issus list. There could be an option to click on the title bar or have an option in the 3 dots menu to "Go to repo page" or similar. |
And the back button mentioned here is the title bar back button or navigation bar back button? If the former, that's intended. |
@maniac103 Both of them does this. Why is this a feature? I personally find it a bit annoying. If the goal was to at the end be on the "Project's" issue list than this could be solved by the title thing I mentioned. |
At step 3, the title bar back button should go to the project's issue list, while the navigation bar back button should go back to the my issues list. That way you can both navigate temporally (that is, back to the last activity you were seeing) and hierarchically (upwards in the repo, here: issue -> issue list -> repo -> owner). If the navigation bar back button does not go back to the my issues list, I need to look into that. |
@maniac103 Never mind. It's the way you described. It's still confusing though. If I wouldn't have made this issue I would've probably never found out. I still stand by my suggestion. |
When a user selects an issue from it's issues, after a while if navigating back one time, it does not go back to the other issues the user has, instead it goes into the repo the issue is submitted to.
From there, many back exit presses have to be made to go back. From the issue list it goes to the repo page, from there it goes to the user that made the repo then it gets back.
Instead let's stay on the users issue page, and let the title or the "developer/repo" text navigate to the repo's homepage where the user could navigate into the "developer" page as well as the issues page without ever interacting with the back button.
I don't know if other functions do the same as well, for those I suggest the same.
The text was updated successfully, but these errors were encountered: