Scroll the product catalogue with touch gestures on a phone

User intention

Browse the product catalogue on my phone.

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 mobile catalogue

The orange circle and trail visualize the recorded touch gesture. The upward swipe leaves All products and opens a product detail page.

AfterThe same script once the merged fix is applied

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

The orange circle and trail visualize the same recorded touch gesture. After the upward swipe, All products remains open without navigating into a product.

How is it judged?

01 · Given

Restore the data and starting state.

A signed-in user is viewing the loaded All products list in a phone-sized touch viewport. Product rows provide access to individual product details.

02 · When

Perform the interaction.

The user swipes upward across a product row and releases the gesture.

03 · Judge

Rationale: Merchants browse the product catalogue to review their inventory and open individual products when needed. On a phone, swiping across product rows is a normal way to browse the list; it should not be mistaken for choosing a product to open.

Require

A swipe across a product row is treated as scrolling rather than opening the product. All products remains visible after the gesture ends.

Allowed

A movement threshold, gesture cancellation, scroll state, or delayed activation may distinguish tap from drag.
Taps, keyboard activation, or a separate details button may open product details.
Scrolling may be short, have momentum, or stop at a boundary while the drag retains the list context.