Repository navigation
fix(snippets): report a tracking snippet without interactions as tracking, not as an error - #324
Merged
Merged
Conversation
…king, not as an error INP (getINP() and getINPDetails()), Interactions and Input-Latency-Breakdown returned status error before any interaction, so the extension showed it as a failure and the CLI counted the snippet as failed. Nothing failed: someone has to use the page first. They return status tracking with a message and their getDataFn, which is what tracking means in snippets/SCHEMA.md, and the schema keeps error for a snippet that failed. The CLI reads such a snippet again while it is still tracking after a click or a key press, reports it as not measured with its message in the human and markdown reports, and no longer exits with 1 for it. The MCP server describes the state in read_results, the INP page in its troubleshooting, and the extension shows it in the colour of information instead of the one of a warning.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The changelog keeps both sections of Unreleased: Added, from the audit filter of the extension (#323), and Changed, from this pull request.
…n is not measured The interaction workflow page said that interactions and input-latency report an error when the script has a click but the page records no interaction. They are reported as not measured and do not count as errors.
nucliweb
added a commit
that referenced
this pull request
Oct 25, 2026
The changelog of the CLI keeps the entries of both pull requests under Unreleased, and the page of the CLI keeps the wording of #324, not measured, with INP among the steps that need a click and the exception of a budget that needs their metric.
This branch was successfully deployed
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
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.
Summary
Before any interaction, INP, Interactions and Input-Latency-Breakdown returned
status: "error". The extension showed it as a failure, in red, and the CLI counted the snippet as failed and exited with1. Nothing failed: someone has to use the page first. That is whattrackingmeans in the contract.getINP(),getINPDetails(),getInteractionSummary()andgetInputLatencyBreakdown()returnstatus: "tracking"with amessage(No interactions yet: click, tap or type on the page, then call getINP() again.) and theirgetDataFn.getINPDetails()keepscount: 0anditems: [].snippets/SCHEMA.md: a window function returnstrackingwhen there is nothing to report yet and someone has to act first, anderroronly for a snippet that failed.tracking, as it did while it returnederror. The human and markdown reports show it asnot measuredwith its message, and it no longer counts as a failed snippet, so it does not make the command exit with1. There is no INP budget today; one should fail when INP was not measured.read_results, and the INP page in its troubleshooting.trackingin the blue of information instead of the yellow of a warning.The changelogs tell whoever retried on
errorto retry ontracking. The skills,dist/andllms-full.txtare regenerated.Screenshots of the panel after Read result with no interaction: INP, Interactions and Input-Latency-Breakdown.
Test plan
getINP()andgetINPDetails()before any interaction aretrackingwith theirgetDataFnand the message, and noerror; the same for Interactions and Input-Latency-Breakdown;read_resultsof the MCP server on a session with nothing recorded givestracking. They failed before the change.trackingresult shows asnot measuredwith its message in the human and markdown reports, without the error marks. They failed before the change.check:emoji, CLI unit 331 of 331, CLI e2e 577 of 577,test:skills179 of 179,test:site44 of 44,test:extension66 of 66,test:extension:e2e77 of 77 (local).--snippet INPon a page without interaction steps prints· INP not measured: …and exits with0; onmainthe same run printedINP undefined.