IntersectMBO / IntersectMBO/govtool
🐛 Live Voting Page Shows "No Results" After Using Interface Back Button Following Idle Period (Wallet Disconnected)
- Dominant language
- HTML
- Stars
- 21
- Forks
- 29
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
Description
### Area
Voting Pillar
### Domain
gov.tools
### Which wallet were you using?
Eternl 2
### Context
When the wallet is **disconnected**, navigating between the **Live Voting** page and individual **governance action details** works correctly — at first. However, if the user remains idle or switches browser tabs for a period of time (duration yet to be fully reproduced), using the **interface Back button** causes the Live Voting page to display **"No results for the search"** instead of the list of proposals. This broken state is resolved only through a hard browser refresh, suggesting a frontend cache/state issue.
### Steps to reproduce
1. Disconnect your wallet.
2. Go to the **Live Voting** page on GovTool.
3. Open any governance action to view its **details**.
4. Use the **interface Back button** to return — works as expected.
5. Remain **idle for some time** or **switch tabs** (duration not yet reliably reproduced).
6. Click the **interface Back button** from a governance action details page.
7. Observe that the Live Voting page now shows **"No results for the search."**
8. Use a **hard browser refresh** (Ctrl+Shift+R / Cmd+Shift+R) to restore correct behavior.
### Actual behavior
- After an idle period, using the **interface Back button** results in a blank governance action list with the message "No results for the search."
- The frontend does not re-fetch or repopulate the proposal list.
- Manual refresh is required to restore expected behavior.
### Notes
- Wallet remains disconnected throughout.
- Idle duration or exact trigger for bug is **not yet reliably reproduced**.
- Does **not** happen immediately — only after an extended tab switch or inactivity window.
### Expected behavior
- Live Voting page should always reload proposals correctly, even after periods of inactivity.
- Interface Back button should trigger a fresh fetch or reuse cached data appropriately.
- No need for user to manually refresh the page to restore data.
Contributor guide
Assessment
This issue has not been assessed yet.