Skip to content

Commit 0fa9c02

Browse files
committed
WebResourceResponseReceived API doc Rev 3
1 parent b73646a commit 0fa9c02

1 file changed

Lines changed: 6 additions & 9 deletions

File tree

specs/WebResourceResponseReceived.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,12 @@ request as it was committed, including modifications made by the network stack
2121
to view the actual request and response for a web resource, but modifications
2222
made to these objects are ignored.
2323

24-
The host app registers for this event by providing a
25-
`WebResourceResponseReceivedEventHandler` (or delegate) to WebView's
26-
`add_WebResourceResponseReceived`/`WebResourceResponseReceived`. When invoking
27-
the handler, the WebView will pass a `WebResourceResponseReceivedEventArgs`,
28-
which lets the app view the request and response. The additional
29-
`PopulateResponseContent` API is exposed from the event arguments so the app
30-
can get the response's body (if it has one). If the app tries to get the
31-
response content before calling `PopulateResponseContent`, the stream object
32-
returned will be null.
24+
When the event is raised, the WebView will pass a
25+
`WebResourceResponseReceivedEventArgs`, which lets the app view the request and
26+
response. The additional `PopulateResponseContent` API is exposed from the event
27+
arguments so the app can get the response's body (if it has one). If the app
28+
tries to get the response content before the first call to
29+
`PopulateResponseContent` completes, the stream object returned will be null.
3330

3431
# Examples
3532
The following code snippets demonstrate how the `WebResourceResponseReceived`

0 commit comments

Comments
 (0)