docs: native-ref dispatch path is web-only in production#1095
Merged
Conversation
tapTarget/fillTarget are wired solely to the web provider's clickRef (interaction-runtime.ts); apple/android backends never define them. Found while designing the #1088 retirement experiment, which this dissolves: the hypothesized iOS runner round trip does not exist.
Size Report
Startup median (7 runs, lower is better):
Top changed chunks: no changes in the largest emitted chunks. |
Member
Author
|
Review status: no actionable blockers found. I verified the key premise with a code search: apple/android platform code does not implement backend tapTarget/fillTarget; the production ref-native path is the web provider clickRef/fillRef wiring through interaction-runtime. That matches the now-closed #1088 conclusion, so the registry row correction is useful and prevents the matrix from implying mobile reach. Focused validation on e5ab92f:
GitHub checks are green (20/20). Added ready-for-human. |
thymikee
added
the
ready-for-human
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While preparing the #1088 B-arm (Maestro suite with native-ref disabled), verification showed the experiment was moot:
tapTarget/fillTargetappear zero times in the apple/android platforms — the only production wiring iswebProvider?.clickRef(src/daemon/handlers/interaction-runtime.ts). The iOS Maestro suite can never exercise this path, so an A/B there would have compared identical binaries and produced a confidently wrong conclusion.Records the fact on the registry row so the matrix stops implying mobile reach. Recommend closing #1088: there is no iOS round trip to retire, and web's stable-handle clickRef is clearly worth keeping.