Current setStatus() shows ONE status message at a time, so the user only ever sees the first failure or the final success. The "guide users through all steps" goal wants something richer: a checklist that ticks each step off as it completes, leaving the previous successes visible.
Suggested shape
✓ Signer extension detected (Podkey)
✓ Public key shared by extension
✓ DID document found at solid.social
✓ WebID resolved: https://test.solid.social/profile/card.jsonld#me
→ Redirecting to https://test.solid.social/…
On a failure mid-flow, the checklist freezes at the failing step, marks it red with the diagnosis, and surfaces the same coaching links the current 0.0.1 message already has.
Implementation sketch
- Replace
setStatus() with addStep(label, state) where state ∈ { pending, ok, error }
flow() becomes a series of addStep(...) calls, mutating each one's state as it progresses- DOM: an
<ol> under the button, with CSS for the three states
Refs
Current
setStatus()shows ONE status message at a time, so the user only ever sees the first failure or the final success. The "guide users through all steps" goal wants something richer: a checklist that ticks each step off as it completes, leaving the previous successes visible.Suggested shape
On a failure mid-flow, the checklist freezes at the failing step, marks it red with the diagnosis, and surfaces the same coaching links the current 0.0.1 message already has.
Implementation sketch
setStatus()withaddStep(label, state)wherestate ∈ { pending, ok, error }flow()becomes a series ofaddStep(...)calls, mutating each one's state as it progresses<ol>under the button, with CSS for the three statesRefs