"back" button navigation on collections seems to loop navigation
Expected behaviour
Navigation does not loop
Current behaviour
If i navigate to a collection then click the "<-back to xxx" button in the bcms (not the browser button) it takes me back to the org page (which I expected), then if i click the "<-back" again it takes me to the same collection, and then it’s just a loop (see video)
---- vs If click “<-back” from a book that has no collection, it takes you back to the org, and then the back button disappears
---- additionally having this back button in the org replaces the org name, which means that when I’m on the org dashboard, there’s no way to know WHERE i am… this is not the case when there is no collection
• When navigate from collection to org • vs when navigate from book (without collection) to org
Steps to reproduce
127.0.0.2_3390_-_Remote_Desktop_Connection_2022-08-02_14-02-58_Trim
- navigate to a collection
- click back (leads to org)
- click back again (leads to collection)
- ...etc in a loop
NCBI's priority feedback
Does not affect content or migration - this can wait until after deployment
QA Steps
- Go to a collection which has books
- Open a book inside a collection
- check the back button on the book- it should send you back to the collection page. Click it.
- Now on the collection page, the back button should send you to the org dashboard and not back to the book.
- Open the toc of collection and check that the back button there doesn't create a loop either.
Proposed solution
We need to remove back button on the collection dashboard. If user wants to go back they can user browser back button. The reason for this is to show the Org name and to prevent a loop.
Further changes here won't affect URLs.