Skip to content

Commit a3bb387

Browse files
committed
update documentation; emphasize the importance of using grid for estimating coordinates
1 parent ea0b6cd commit a3bb387

3 files changed

Lines changed: 7 additions & 7 deletions

File tree

configs/examples/general_purpose.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,9 @@ web_agent:
9292
- Base your judgement on visual appearance and behaviour, not on source code.
9393
- If the page shows a blank white page or an error message, check console log and report that clearly.
9494
95-
## Estimating Coordinates with the Grid
95+
## Estimating Coordinates with the Grid (CRITICAL)
9696
When you need to click, type, or interact with a specific element and you are unsure of its exact pixel position:
97-
1. Take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
97+
1. ALWAYS take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
9898
2. The screenshot will show red grid lines with x/y labels along the edges.
9999
3. Read the grid labels to estimate the x/y pixel coordinates of the target element.
100100
4. Use those coordinates to estimate the position in your click/type/hover call.

configs/examples/swebench_multimodal.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -114,9 +114,9 @@ web_agent:
114114
- Base your judgement on visual appearance and behaviour, not on source code.
115115
- If the page shows a blank white page or an error message, check console log and report that clearly.
116116
117-
## Estimating Coordinates with the Grid
117+
## Estimating Coordinates with the Grid (CRITICAL)
118118
When you need to click, type, or interact with a specific element and you are unsure of its exact pixel position:
119-
1. Take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
119+
1. ALWAYS take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
120120
2. The screenshot will show red grid lines with x/y labels along the edges.
121121
3. Read the grid labels to estimate the x/y pixel coordinates of the target element.
122122
4. Use those coordinates to estimate the position in your click/type/hover call.

configs/examples/webgen_bench.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -90,12 +90,12 @@ web_agent:
9090
- Base your judgement on visual appearance and behaviour, not on source code.
9191
- If the page shows a blank white page or an error message, check console logs and report clearly.
9292
93-
## Estimating Coordinates with the Grid
93+
## Estimating Coordinates with the Grid (CRITICAL)
9494
When you need to click, type, or interact with a specific element and you are unsure of its exact pixel position:
95-
1. Take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
95+
1. ALWAYS take a screenshot with `grid=true` (optionally set `grid_spacing` for finer resolution, e.g. 100).
9696
2. The screenshot will show red grid lines with x/y labels along the edges.
9797
3. Read the grid labels to estimate the x/y pixel coordinates of the target element.
98-
4. Use those coordinates in your click/type call.
98+
4. Use those coordinates to estimate the position in your click/type/hover call.
9999
You do NOT need to use the grid for every screenshot — only when you need to pinpoint coordinates.
100100
101101
## Actively interact with the page

0 commit comments

Comments
 (0)