From b4bee4915225dd2d0c132c76a58fb208f3c5dff5 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Thu, 24 Nov 2022 13:12:32 +0100 Subject: [PATCH] docs: document how to import DEFAULT_INTERCEPT_RESOLUTION_PRIORITY (#9324) Closes #9236 --- .../version-19.3.0/guides/request-interception.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/versioned_docs/version-19.3.0/guides/request-interception.md b/website/versioned_docs/version-19.3.0/guides/request-interception.md index b1591ec10f1..521af64b7b7 100644 --- a/website/versioned_docs/version-19.3.0/guides/request-interception.md +++ b/website/versioned_docs/version-19.3.0/guides/request-interception.md @@ -175,7 +175,7 @@ Intercept Mode: - In the event of a tie, `abort` > `respond` > `continue`. For standardization, when specifying a Cooperative Intercept Mode priority use -`0` or `DEFAULT_INTERCEPT_RESOLUTION_PRIORITY` (exported from `HTTPRequest`) +`0` or `DEFAULT_INTERCEPT_RESOLUTION_PRIORITY` (`import {DEFAULT_INTERCEPT_RESOLUTION_PRIORITY} from 'puppeteer'`) unless you have a clear reason to use a higher priority. This gracefully prefers `respond` over `continue` and `abort` over `respond` and allows other handlers to work cooperatively. If you do intentionally want to use a different priority,