Project

General

Profile

Bug #39121

mgr/dashboard: Cancel button leads to the previous page in browser history

Added by Ernesto Puerta over 4 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
UX
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Tags:
usability, low-hanging-fruit

Description

After back button refactoring, the behaviour of the Back/Cancel button has changed:
- Previously it was based on the Router hierarchy (e.g.: #/pool/create's back led always to #/pool)
- Now it uses location.back() method, which relies on the browser history (e.g: #/pool/create is accessed via URL, after clicking Cancel the browser will show the browser home page, not #/pool or any other dashboard page).

No matter this is acceptable behaviour or not, it means a change in the way the user browses the dashboard.

An alternative to this could be to use existing information provided to the Routing module.

History

#1 Updated by Lenz Grimmer over 3 years ago

  • Tags set to usability, low-hanging-fruit
  • Target version deleted (v14.2.0)

#2 Updated by Ernesto Puerta over 2 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 152 to UX

#3 Updated by Seremba Patrick over 1 year ago

Hi @Ernesto, just for the sake of clarity, do you want the back button to get back to its behavior before refactoring? Or did I get the issue wrong? Secondly, do you have any hints or pointers on how one can tackle this issue? Thanks a lot.

Also available in: Atom PDF