[Stefan3002]

Done

• Allow users to pass custom onClick event handler when clicking the button of a segmented controls.
• This would allow users to do custom logic such as navigating to a different slug and showing the dynamic content there. (maybe they want to keep a different URL for all of the cases)

QA

Pinging @canonical/react-library-maintainers for a review.

QA steps

• Run storybook
• Navigate to the SegmentedControls component
• Verify that it prints in the console a message when clicking a certain segmented control button

Percy steps

• No visual changes expected

Fixes

Fixes: #AC-4750.

[Copilot]

🟡 Changes recommended

Type the callback as a mouse-event handler and forward the click event.

1 open finding

• Type segment onClick as a button mouse event handler · New

What changed in this PR

Adds optional per-segment click handlers to SegmentedControl, with tests and Storybook examples.

Changes:

• Adds optional onClick callbacks to segments.
• Invokes callbacks when buttons are clicked.
• Adds test coverage and usage examples.

File	Summary
src/​components/​SegmentedControl/​SegmentedControl.tsx	Adds segment click callback support.
src/​components/​SegmentedControl/​SegmentedControl.test.tsx	Tests callback invocation and selection behavior.
src/​components/​SegmentedControl/​SegmentedControl.stories.tsx	Demonstrates callback usage.

🧠 Review effort: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟢 Approval recommended

No unresolved issues were identified that would block approval.

0 open findings

1 resolved since last review

• Type segment onClick as a button mouse event handler

🧠 Review effort: Lite

[bartaz-canonical]

LGTM, good catch

[github-actions]

🎉 This PR is included in version 4.14.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀