-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Horizontal Steppers #29
Comments
I think its a great request. We've got a few other priorities to tackle first, but I wanted to acknowledge that this will stay on our radar. |
Yeah totally agree, good request @Daeluse thx! |
I think it would be nice to have these two attributes/settings:
|
Yes, i was kinda thinking already in my mind to just add an input property that changes the stepper from vertical to horizontal depending on a value (boolean, enum or whatever). Leveraging our |
Added with #95. Its a first draft on |
chore(): add demo app to test code-editor
chore(): add demo app to test code-editor
…eradata#29) * fixed typos * added echarts to peerDependencies * added echarts peerDependencies * docs(): tweak
Feature Request For Horizontal Steppers
Spec Sheet - https://material.google.com/components/steppers.html#steppers-types-of-steppers
What is the expected behavior?
Instead of leveraging the behavior of Material Lists, leveraging or extending the behavior of Material Tabs will provide a Horizontal Stepper which displays progress stacked on top of current step content in a column fashion rather than a row. Switching between steps would have some sort of 'swiping' animation and would emit the same events currently emitted by the vertical stepper.
What is the motivation / use case for changing the behavior?
Horizontal Steppers provide a much better user experience for wizards because they keep content above the fold and display progress before content. They also have better reaction to Wide Screen sizes.
What would you like to see in addition to expected behavior?
Development would be greatly simplified if a path towards switching between horizontal and vertical on the fly could be made for when the desktop layout turns to mobile.
The text was updated successfully, but these errors were encountered: