cancel all new network requests

Author: sadym-chromium

index.bs

@@ -9124,6 +9124,29 @@ and |user context| are:
 
 </div>
 
+<div algorithm>
+The steps to <dfn>get emulated network conditions</dfn> given |related navigables|
+are:
+
+1. For each |navigable| of |related navigables|:
+
+   1. Let |top-level traversable| be |navigable|’s [=navigable/top-level traversable=].
+
+   1. Let |user context| be |top-level traversable|'s [=associated user context=].
+
+   1. For each |session| in [=active BiDI sessions=]:
+
+      1. If |session|'s [=emulated network conditions map=] [=map/contains=]
+         |top-level traversable|, return
+         [=emulated network conditions map=][|top-level traversable|].
+
+      1. If |session|'s [=emulated network conditions map=] [=map/contains=]
+         |user context|, return [=emulated network conditions map=][|user context|].
+
+1. Return null.
+
+</div>
+
 <div algorithm>
 The [=remote end event trigger=] is the <dfn export>WebDriver BiDi before
 request sent</dfn> steps given |request|:
@@ -9228,8 +9251,17 @@ request sent</dfn> steps given |request|:
 
     Note: While waiting, no further processing of the request occurs.
 
+1. Let |emulated network conditions| be the result of
+   [=get emulated network conditions=] with |related navigables|.
+
+1. If |emulated network conditions| is not null and
+   |emulated network conditions|["<code>offline</code>"] is true, return
+   ([=network error=], "<code>complete</code>").
+
 1. Return (|response|, |response status|).
 
+Issue: Respect return value in Fetch's "HTTP-network-or-cache fetch" algorithm.
+
 </div>
 
 #### The network.fetchError Event #### {#event-network-fetchError}