[v4]: add `/elementInfo` route stub
Merged
SE
8mo ago+582+582+012345678901234567890123456789-0-0-0123456789
why
- to add a single
/elementInforoute which encapsulates multiplelocatorfunctions
what changed
- added an
/elementInforoute, which accepts aSelector, and returns the following info:countisVisibleisCheckedinputValuetextContentinnerHTMLinnerTextcentroid
screenshot:
test plan
- added a test which verifies that the
/elementInforoute accepts a request
Summary by cubic
Adds the v4 page.elementInfo endpoint (POST /v4/page/elementInfo) to fetch common element details in one call. The handler is a stub that returns defaulted fields to unblock client work.
- New Features
- Implemented
page.elementInforoute that accepts aSelectorand optionalfieldsfilter; returns:count,selector,tagName,backendNodeId,visibility,domRects,content, and optionalinputInfo,ariaInfo,attributes,styles. - Wired the route into v4 page routes, added request/action/result/response schemas to OpenAPI, and added an integration test posting an XPath selector to assert a successful action.
- Implemented