Skip to content

Add ProgressTabs process stepper - #145

Merged
terpimost merged 38 commits into
mainfrom
codex/progress-tabs
Aug 23, 2026
Merged

Add ProgressTabs process stepper#145
terpimost merged 38 commits into
mainfrom
codex/progress-tabs

Conversation

@Xapollon430

Copy link
Copy Markdown
Member

Summary

  • add the controlled and uncontrolled ProgressTabs process stepper with four statuses, three sizes, horizontal and vertical layouts, and customizable navigation
  • preserve Tabs interaction semantics while keeping ProgressTabs styling and DOM composition isolated
  • add consumer documentation, live examples, generated package docs, and changelog coverage
  • prevent unchanged changelog notifications from retriggering the docs development watcher

Verification

  • pnpm run lint
  • pnpm run typecheck
  • pnpm run build
  • pnpm --filter anta-site run build

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 7, 2026

Copy link
Copy Markdown

Deploying anta with  Cloudflare Pages  Cloudflare Pages

Latest commit: cbd6b44
Status:⚡️  Build in progress...

View logs

@Xapollon430
Xapollon430 requested a review from terpimost as a code owner August 7, 2026 15:55
@terpimost

Copy link
Copy Markdown
Contributor

What do you think about renaming it to StepTabs? Or just Steps?

I'm afraid of having extra Prev/Continue buttons inside the shadow dom. I'm not against providing such options on JSX but I think it is just additional things that consumers could compose. So I suggest to not have those Prev Next buttons because people could configure and just pass them separately... If anything we should dedicate space and teach how to perform capture of the event and switching tabs in a controlled way...

I found that the best references would be:

And I think we should have flexibility for consumers to be able to assign any icon/number letter and easily change background look of the step, and the line too.
We should support label and hint, and tones for tabs

I think size is a bit shifted to the small:
image

And tab title shouldn't feel like it is smaller than the content, the example should probably use <Text component with appropriate sizing.

Why do we need a special component instead of customizing Tabs? Because of extra statuses on StepTabs?

@terpimost
terpimost force-pushed the codex/progress-tabs branch from 4d3c1a7 to 6a49995 Compare August 23, 2026 03:10
- selected neutral loader inherits marker foreground (was invisible on primary)
- loader tones defer to forced-colors CanvasText
- vertical panel parks after last step when value matches no option
- note the display:contents a11y tradeoff
- drop stale Steps 'Changed' changelog entry
The completed-connector color was rebuilt in CSS from separate lightness,
chroma, and source knobs, then overridden across light/dark/tone/vertical.
Those values resolve exactly to the existing --border-2 / --border-2-<tone>
tokens, so point at the tokens instead. Rename the active marker border to
--steps-marker-active-border (mirroring --steps-marker-rest-border) so the
connector can reuse Tabs' per-tone --tab-selected-border. No visual change.
@terpimost
terpimost merged commit 29d346c into main Aug 23, 2026
2 of 3 checks passed
@terpimost
terpimost deleted the codex/progress-tabs branch August 23, 2026 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants