diff --git a/assets/images/smartui-hooks-region-ignore/coordinate-rectangle.png b/assets/images/smartui-hooks-region-ignore/coordinate-rectangle.png
new file mode 100644
index 000000000..75fa8970f
Binary files /dev/null and b/assets/images/smartui-hooks-region-ignore/coordinate-rectangle.png differ
diff --git a/docs/smartui-hooks-region-ignore.md b/docs/smartui-hooks-region-ignore.md
index f41bec295..c3f35b0d2 100644
--- a/docs/smartui-hooks-region-ignore.md
+++ b/docs/smartui-hooks-region-ignore.md
@@ -59,6 +59,10 @@ This gives the Web Hooks path the same region controls already available on RD H
Pass a `coordinates` entry (a list of `"x1,y1,x2,y2"` strings) under `ignoreDOM`. SmartUI excludes those rectangles from the comparison. The four values are the left, top, right, and bottom edges of the rectangle in pixels.
+
+
+For example, `"50,50,300,300"` defines the region whose top-left corner is at `(left=50, top=50)` and whose bottom-right corner is at `(right=300, bottom=300)` — a 250 × 250 rectangle.
+
@@ -190,6 +194,7 @@ config.ignoreDOM = {
cssSelector: ['.promo'], // selector
coordinates: ['847,185,1571,734'], // coordinates
};
+await driver.executeScript('smartui.takeScreenshot', config);
// both regions are ignored
```
@@ -201,19 +206,13 @@ config["ignoreDOM"] = {
"cssSelector": [".promo"], # selector
"coordinates": ["847,185,1571,734"], # coordinates
}
+driver.execute_script("smartui.takeScreenshot", config)
# both regions are ignored
```
-## Behaviour summary
-
-| Input mode | How you pass it (under `ignoreDOM` / `selectDOM`) | Resolved against | Result |
-|------------|---------------------------------------------------|------------------|--------|
-| Selector | `id` / `class` / `xpath` / `cssSelector` | Live DOM (`getBoundingClientRect()`) | Region of the matched element(s). |
-| Coordinate | `coordinates: ["x1,y1,x2,y2"]` | The produced-image space (viewport or full page) | Exactly the supplied rectangle. |
-
## Validation and errors
Coordinates are validated at two levels — note that only the **format** check happens on the hooks ingestion path; **page-bounds** elimination is a downstream comparison-engine behaviour, not part of the hooks request validation:
@@ -225,7 +224,6 @@ Coordinates are validated at two levels — note that only the **format** check
## Notes
-- **Scope:** this applies to the Web Hooks path (Selenium `executeScript("smartui.takeScreenshot", ...)`). RD Hooks and the CLI SDK already support these inputs.
- **Empty or mixed configs:** a config containing only `coordinates` (no selector) is honoured — it is not treated as "no DOM region." Selector and coordinate regions in one `ignoreDOM` are additive.
- **Identical to selector-based ignore:** coordinate regions resolve to the same kind of ignored/selected box as selectors, so the comparison result matches an equivalent selector-based ignore.