Web UI: back button always returns user to view with a stale query - current query gone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
I am seeing this scenario where I generate a query, then I click on one of the nodes in that query to get the nodes view, but I go back, I return to an old view with a different query.
Since I think I found a way to recreate it and am able to clearly see separate behaviors for same action, I am opening this bug:
Here are steps that I think will recreate this on Chromium:
1) Edit the query field on the main view. Click on a server in the list then click on the back button. It gets you back to previous vew with the query still active and query looks ok.
2) Edit the query field again and repeat.. Going back still looks good, and I continue to see list with freshly edited query.
3) Now, clear the query so all the servers are now in the list, and click on of those servers to get the server view, go back and it will return you to a previous query.
4) From that point on, no matter how many time you repeat (edit query, click on node and hit back button), you will always get that same stale query view. It's not going to go away! ... unless you restart from scratch of course.
It's strictly a UI issue and can be a bit of an annoyance since it wipes out user's current query.
Workaround for me is to use the Open link tab, but I seem to run most often into bug 1484696 when I navigate to the node's view in this manner.
summary: |
- Web UI: back button returns to view with a stale query in web UI - + Web UI: back button always returns user to view with a stale query - current query gone |
tags: | added: ui |
Changed in maas: | |
milestone: | none → 1.9.1 |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | 1.9.1 → 1.9.2 |
Changed in maas: | |
milestone: | 1.9.2 → 1.9.3 |
Changed in maas: | |
milestone: | 1.9.3 → 1.9.4 |
Changed in maas: | |
milestone: | 1.9.4 → 1.9.5 |
We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.