Repository navigation
v0.6.1
A fix for pages that were wrongly reported as incompletely captured.
Fixed
-
Requests the page cancels itself no longer make a page capture incomplete. Frameworks drop their own requests, for example Next.js cancelling RSC prefetches when the network is slow. In adapter mode such a request used to be stored as
browser-failure, so one cancelled prefetch on a busy server could turn every rule on the start page into "not checkable". (#45)privalint now detects the cancel from Chromium (
Network.loadingFailedwithcanceled), not from error text. It stops the adapter call if it is still running, and records the request askind: 'skipped',skippedReason: 'cancelled-by-page'. That does not restrict the capture, like an omitted beacon, and the URL still counts for the tracker rules. Requests the browser cancels because the page navigates, such as the reload after rejecting, are recorded the same way. Real failures (adapter errors, timeouts, connection, TLS, DNS, limits) still make the capture incomplete.
Report format
New reports use schema 1.2.0, which adds the skip reason cancelled-by-page. Schemas 1.0.0 and 1.1.0 are unchanged and still supported by identifyReportSchema().
If you validate reports against a pinned schema file, add privalint/schemas/report-1.2.0.schema.json (and sarif-properties-1.2.0.schema.json). A validator that only knows 1.1.0 will treat new reports as an unsupported version.
Full changelog: https://github.com/JExcellence/privalint/blob/main/CHANGELOG.md