Active stepped-list state
Pattern to amend
We have cases where highlighting an active step would be useful.
Visual

Context
Tutorials: https://ubuntu.com/tutorials/how-to-ubuntu-core-recovery-mode#1-overview
Not exactly same pattern, but snapcraft has similar use case and they use accordion for that:
@anthonydillon would it work for you if we apply the default active opacity on a class called is-active?
Yeah sure, what way to show the currently active item. Not sure it's very clear from your image. But something like that.
Ok, we ca ntake the colours freom the chips, which have the same base colour. The active will be a little darker. This is ready for dev then @bartaz.
@amylily1011 is going to work on this as a pattern for this cycle
WG: work planned for the 28th of March
@amylily1011 can you please update here with the link to the docs, then close this issue, thanks
This is the spec for the stepper: https://docs.google.com/document/d/1jh0eUSRtjEe-qqQTXv1rtZGvnOqOT29o53EVDd8g4dw/edit
WG: @lidia-luna is going to organise usability testing to move this forward.
This is now published on discourse and testing will start soon.
Reopening this issue as the testing was done and got a bit forgotten but the component is still very much needed. The results of the testing are here. They show that, mostly, the stepper works and is designed as expected. The only aspect that is not clear is whether the past steps are clickable and whether they'd lose progress by going back.
WG: we agree to build it as is in the spec and keep an eye on the implementation in case there is any further confusion. We are concerned particularly about whether the user understands if the current step is completed or not. MAAS might build a stripped down version of this this cycle (24.04).
@danielmutis What's the latest status of this? Is this ready for implementation?
Yes, it's ready to implement. If anyone wants to amend the component they can submit issues independently.
Triaging: effort low/medium, impact low/medium.
Do we need this now, or can it wait? Needs decision.
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/WD-15157.
This message was autogenerated
Design systems contribution meeting:
- We consider this to be ready for development.