Open a catalogue product in a new tab using native browser gestures

User intention

Review a product's details while browsing the catalogue.

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 · Review the product catalogue

Compare the browser context menu and tab bar. The product row has no Open link in new tab entry, and the subsequent click replaces the product list in the same tab.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0 · Review the product catalogue

The product row exposes native link actions. Aurora Desk Lamp opens in a separate tab while the original product list remains available.

How is it judged?

01 · Given

Restore the data and starting state.

A signed-in catalogue manager is viewing Catalog > Products, with Aurora Desk Lamp visible in the loaded list.

02 · When

Perform the interaction.

The user right-clicks the product name to inspect the browser menu, dismisses it, and middle-clicks the same name. They inspect the page that opens and, if a separate tab opened, return to the catalogue.

03 · Judge

Rationale: Catalogue staff may review individual product details as they browse the product list. Familiar browser link actions let them open those details separately and continue browsing without having to find their place in the catalogue again.

Require

Product names offer discoverable browser link actions on right-click. Middle-click opens the correct product in a new tab and preserves the original catalogue list and its state.

Allowed

Ctrl/Cmd-click and ordinary left-click navigation may also be supported.
Native links and optional keyboard- or touch-accessible new-tab actions may support or supplement the required browser gestures.
The destination may be the product overview or edit page while opening the correct product and preserving the original list.