route-graphics 1.28.0 → 1.29.0

package/README.md

@@ -98,6 +98,31 @@ WebGPU device loss emits `rendererContextLost`; because a lost WebGPU device is
 not restorable, consumers must recreate the Route Graphics instance rather than
 wait for `rendererContextRestored`.
 
+### Semantic bounds hit testing
+
+`hitTestElementBounds({ x, y })` accepts renderer-space coordinates and returns
+all hit branches from front to back. Each branch contains a root-to-deepest
+`path`; every path entry includes the semantic element `id`, `type`, and live
+world-space bounds. `bounds.corners` preserves rotation and
+`x`/`y`/`width`/`height` is the enclosing axis-aligned rectangle. Container
+scroll offsets and viewport clipping are applied, while opacity and transparent
+pixels do not create click-through holes.
+
+```javascript
+const hits = app.hitTestElementBounds({ x: pointerX, y: pointerY });
+const frontmostPath = hits[0]?.path ?? [];
+```
+
+Route Graphics deliberately returns rendered semantic identities rather than
+editor document identities, and it does not apply consumer-specific filtering.
+Consumers remain responsible for mapping each render occurrence to an authored
+selection owner and ignoring any renderer elements they do not want to select.
+
+Bounds queries are observational. They do not alter or suppress existing
+hover, click, drag, keyboard, input, slider, or scroll behavior. A consumer can
+therefore observe a pointer gesture for selection while Route Graphics
+continues processing the same authored interaction.
+
 For complete usage details, go to:
 
 - [Getting Started](http://route-graphics.routevn.com/docs/introduction/getting-started/)