Summary Page - Recent Activity Log Bug
50 followers
0 Likes
We are currently inviting our members to our CX community, and we are having quite a bit of recent activity being logged on our Summary page. When I scroll through the pages of activity, I often click on the profile of a new member. After viewing the member's profile, I proceed by clicking the back button to go back to the summary page where I left off. However, the back button takes me all the way back to page (1), and I have to scroll back through all of the recent activity to get back to where I left off. This is obviously very cumbersome process. It might be my browser version, or just an oversight. I hope that this is an issue that can be addressed within a reasonable time period.
Thank you,
Sulaiman
2 Replies
Reply
Subgroup Membership is required to post Replies
Join Groupsite Champions now
Suggested Posts
| Topic | Replies | Likes | Views | Participants | Last Reply |
|---|---|---|---|---|---|
| What's Coming Next ... | 25 | 0 | 4325 | ||
| Chat Room participants | 1 | 0 | 1212 | ||
| "Tagging" photos in the galleries | 3 | 0 | 1333 |
The page turning activity goes on _inside_ of the page, it does not create additional history element in the browser. Thus, when you click back on your browser, it simply goes back to the page. Since the only history element for the page is page 1, this is where you end up. The back button bringing you back to where you were is automatic feature of the browser. Changing this is technically possible, but will take some work. This would have to be written from scratch, as it is not an automatic feature because there is only *one* page in your browser history, not one for each page turn.
Sulaiman, I'm going to move this topic into the "New Feature Requests" because it's not truly a bug. It's just the way browsers automatically work with pages in your history. In order to make one page look like multiple "pages", we would have to implement this as a new feature.
Now, if the page turner brought you to a true new page each time, then the browser would have a history item for each one. However, this would require reloading the entire summary page each time and the user would have to wait for that and for the browser to scroll back down to the list that they were paging to. This is would make it less usable.
So, it probably better to leave it as an "in-page" update, and try to add custom back button logic.