"Results per page" doesn't change when using "Back" button in Chrome and IE11

Bug #1834792 reported by Kristina Hoeppner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Confirmed
Medium
Unassigned

Bug Description

When you are on a page where you can select the "Results per page" and you set it to a high number, it doesn't go back to the original number yet still displays the paginator when you return to the page via the "Back" button. This is an issue observed in Chrome and IE11. IT doesn't happen in Firefox. Not tested in Safari yet, but will need to be checked there as well.

To replicate:

1. Create 30 user accounts on your site via CSV upload.
2. Go to Main menu -> Engage -> People and make sure that you search for "Everyone".
3. Choose "50" in the "Results per page" drop-down menu.
Expected and actual result: The paginator goes away and all 30 people are displayed.

4. Click one of the names.
5. Use the browser's "Back" button to return to the "People" page.
Expected result: The "Results per page" drop-down menu is reset to "10" because the filter is not sticky and the paginator is displayed.
Actual result: The "Results per page" drop-down menu still says "50" yet the paginator is displayed as well.

The same happens for example on the "User search" page in Admin menu -> Users -> User search.

Tags: bite-sized
Revision history for this message
Gold (gold.catalyst) wrote :

When /user/index.php is initially hit the list is prepopulated.

When Results per page is changed a call to friendsearch.php is performed and the list is replaced with the contents from the JSON that is returned.

This could be resolved if the /user/index.php page did not initially populate the results and, instead, triggered a call to friendsearch.php after the page had loaded. Then it could use the value the Results per page is set to.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.