The DRep directory currently randomizes the list of representatives every time the page is visited and continues to refresh the list every few seconds while a user remains idle. This behavior was introduced to ensure fairness by not prioritizing any specific DRep. However, it negatively impacts user experience by making the list unpredictable.
Additionally, browser console logs show that randomization calls to the backend continue even after a user applies search criteria. This leads to an inconsistent experience where filtered results are unexpectedly shuffled, making it difficult for users to navigate and select representatives effectively.
Acceptance Criteria:
- The DRep list should be randomized only once per page visit.
- The list should not refresh or re-randomize while the user is idle on the page.
- If a user applies search criteria, the list should remain static and not trigger further randomization calls.
- Ensure that no unnecessary backend requests for randomization occur after search filters are applied.
- Verify that the fairness goal of initial randomization upon page load remains intact.
The DRep directory currently randomizes the list of representatives every time the page is visited and continues to refresh the list every few seconds while a user remains idle. This behavior was introduced to ensure fairness by not prioritizing any specific DRep. However, it negatively impacts user experience by making the list unpredictable.
Additionally, browser console logs show that randomization calls to the backend continue even after a user applies search criteria. This leads to an inconsistent experience where filtered results are unexpectedly shuffled, making it difficult for users to navigate and select representatives effectively.
Acceptance Criteria: