[himaSH97]

The PR fulfills these requirements: (check all the apply)

• It's submitted to the main branch.
• When resolving a specific issue, it's referenced in the PR's title (e.g. feat: Add a button #xxx, where "xxx" is the issue number).
• When resolving a specific issue, the PR description includes Closes #xxx, where "xxx" is the issue number.
• If changes were made to ui folder, unit tests (make test) still pass.
• New/updated tests are included

[himaSH97]

Fixes #2243

Summary

Adds an optional link property to ui.tab.

When link is set, clicking the tab navigates to the supplied external URL.
Tabs without link retain their current behavior and continue emitting backend
events.

Tests

[mturoci]

Thanks @himaSH97! The PR looks good, just a few comments/questions.

[mturoci]

Code LGTM.

Found 1 minor styling bug for visited link state. Would be better if the visited link style would be the same as non visited (respecting theme color).

Screen.Recording.2026-09-01.at.4.44.25.PM.mov

[himaSH97]

Added a small fix to above styling mismatch. Let me know if this works.

I have added a prevent default for the mouseDown event. it breaks the forcus from the rendered a tag and use the default styling.

[mturoci]

Isn't there a way to just override :visited style for the link? Would be more explicit about the actual intent. The JS solution may also potentially turn off other browser behavior we would desire. Better to just fix styling and not touch anything else.

[himaSH97]

Hi @mturoci,
I tried adding a custom class with the existing css styling but this method gets overridden by pivot link styles

className: css(className, isSelected && classNames.linkIsSelected)

I found it is possible to do this with custom html attribute ('data-external-tab': true) and use that to render the styles which pivot won't override

'.ms-Pivot-link[data-external-tab]:hover, .ms-Pivot-link[data-external-tab]:hover .ms-Pivot-linkContent': {
            color: cssVar('$card')
   }, 

is this a good approach to use here?

[mturoci]

Hey @himaSH97. See b958521 for the proper solution.

I assume your attempts just needed an !important rule. However, we do not want to scope the fix to just tab components, but potentially globally to all the places that framework may need to render links within a Pivot items. The commit above fixes them all uniformly.

I tested around and couldn't find any more issues. Please do the same and let me know in case you still find some bug. If not, I we are good to merge this.