pj 57101df48d fix(runtime): surface unresolved action targets instead of dropping silently ...

serializeAction emitted {x:0,y:0} via `?? 0` whenever a Tap/InputText/Swipe
target failed to resolve to coordinates. The runner then collapsed those
to ErrNoAction, so every selector typo became a silent no-op tick.

Have the runtime return null on unresolved targets and log a console
warning (visible via chromedp's runtime listener). Drop the now-redundant
{0,0} -> ErrNoAction guard so a deliberate Tap at the origin actually
fires.

2026-05-03 11:01:16 +07:00

..

spec

fix(runtime): surface unresolved action targets instead of dropping silently

2026-05-03 11:01:16 +07:00