Skip to content
This repository has been archived by the owner on Oct 22, 2020. It is now read-only.

Make stepper interactive #2271

Open
hdrury1 opened this issue Jul 10, 2019 · 1 comment
Open

Make stepper interactive #2271

hdrury1 opened this issue Jul 10, 2019 · 1 comment
Labels
Client-Side Any issue regarding the look / behaviour of the application in the browser.

Comments

@hdrury1
Copy link
Contributor

hdrury1 commented Jul 10, 2019

Many users are trying to navigate the wizard with the stepper. We should make it possible to do so.

@hdrury1 hdrury1 added the Client-Side Any issue regarding the look / behaviour of the application in the browser. label Jul 10, 2019
@chris-huggins
Copy link

@hdrury1 I suggest we use a solid blue do to show any "incomplete step that is further ahead than the current step" i.e. if the user is on a step but goes back, we show the last step in the state - this ensures they can get back there. Any step beyond the "incomplete step" would be shown in grey and would not be interactive.

e.g. user got to "editors" step and went back to the "details" step

image

Worth noting any step that can be skipped (i.e. is done) would have a tick so it would only be the furthest step that would appear in this state.

e.g. the user went further back to the files step - the details step is still "complete".

image

In the event that the user deletes information or causes a validation on the current step, the question is do we a) prevent them navigating away using the stepper? or b) show the stepper in an error state or use other validation?

I would argue we should scroll to the error if the user tries to navigate away with the stepper (as already planned when pressing "next"). This would be easier than any error states in the stepper

e.g. we should not rely on anything like this because of colour-blindness, and generally I think it requires too much thinking to take in

image

As a result, I think we need to be sure to work on this ticket first to get the "scroll to validation error" behaviour in first

#2071

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client-Side Any issue regarding the look / behaviour of the application in the browser.
Projects
None yet
Development

No branches or pull requests

2 participants