Material-components-web: Investigate making the Stepper

[traviskaufman]

Spec reference: https://www.google.com/design/spec/components/steppers.html

• [ ] All steppers / step types, _except_ "Mobile Step"
• [ ] "Mobile Step"

Caveat: We might want to split this up differently once we get to this task, and recategorize the stepper types from the spec language to make it less ambiguous.

Copied from https://github.com/google/material-design-lite/issues/4501

[ziyafenn]

Would love to see it implemented! :)

[ColbyTJohnson]

Would love to see this as well!

[aaronhudon]

Here's my crack at creating a vertical stepper using the current state of the MDC library.

https://codepen.io/aaronhudon/full/MELydx/

[AndryHTC]

Are there some news?

[yxchng]

Same here

[djensen47]

Were steppers removed from the spec?

[mikaturk]

Will this see the light of day or is this not happening?

[sharpmachine]

What happened to the stepper? The new material design docs don't have it.

[GHXST01]

Is this still happening?

[Praveen-Rai]

Any updates ?

[Praveen-Rai]

I am not sure, what's the rational behind removing steppers from material design. I believe they are basic building blocks, when a step-by-step movement is required in UX flow.

The progress indicators in Material Design spec. lacks the flexibility to show step progress ( which might have been useful to create a work-around for Stepper ). For e.g. i just want to display user's progress in a course ( number of lessons completed, and total number of lessons ). Basic step progress indicator . This isn't pretty, but the best i could get with Materialize & Material Design.

CC @abhiomkar

[abhiomkar]

I sent this to design for response on this request.

[Praveen-Rai]

FYI .. I've raised a related request regarding Determinate Progress Indicators design spec.

[equinusocio]

So steppers are dead... long live to steppers!

[abhiomkar]

Update: Our archived guidance is guidance that wasn't updated with our Material Theming release. We'll let the design team know that there is interest in this!

I'm closing this issue since nothing to implement until design guidance is updated for this component.