Repository navigation
Commit bc5c09d
committed
docs(website): name the two dispatch routes the moving-target check does not cover (#3471)
The paragraph claimed the check runs for any @ref or selector target, which held for neither
exclusion. `click @ref` on a backend that dispatches to the element itself returns from
`maybeTapRefTarget` before the guard is reached, and the Maestro non-hittable coordinate fallback
is a fused runner request that never resolves a point at all. Both are now stated as the exceptions
they are, and "nothing was tapped" becomes "nothing was dispatched" for the same reason the command
metadata changed verb.1 parent 0369c8e commit bc5c09d
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
422 | 422 | | |
423 | 423 | | |
424 | 424 | | |
425 | | - | |
| 425 | + | |
426 | 426 | | |
427 | 427 | | |
428 | 428 | | |
| |||
0 commit comments