Use local tabs in the branch selector

User intention

Browse a repository's branches.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Open the branch selector, hover Branches, and inspect its appearance after activation. The address bar and accessibility roles are outside the recording.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Open the selector and reactivate Branches while inspecting the visible main selection. The recording does not show the URL or accessibility roles.

How is it judged?

01 · Given

Restore the data and starting state.

A public repository's Code page has main selected. Its open ref selector shows the active Branches tab, the alternative Tags tab, and a separate View all branches destination.

02 · When

Perform the interaction.

Hover over and click the already-active Branches tab in the open ref selector.

03 · Judge

Rationale: Branches and Tags select within the current dropdown; View all branches navigates elsewhere. Distinguishing those roles prevents a local action from suggesting navigation or changing the URL unnecessarily.

Require

Expose Branches and Tags as local dropdown-tab actions, with no empty-fragment link or empty # URL change. Preserve tab selection and the separate View all branches destination; reactivating Branches may leave its content unchanged.

Allowed

Conventional button or tab controls with appropriate local-action semantics are acceptable; a specific element tag or CSS class is not required.
Hover color, pointer cursor, and focus treatment may vary, and returning focus to the filter is acceptable.
The active tab may perform no content change; it must not be forced to navigate to /branches.