From 378c4ad6da527c970aad9611e6010da17ac26ccb Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 25 Jan 2015 10:07:22 -0500 Subject: [PATCH] Updated Behind the scene network requests (markdown) --- Behind-the-scene-network-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Behind-the-scene-network-requests.md b/Behind-the-scene-network-requests.md index 57319b4..e13000b 100644 --- a/Behind-the-scene-network-requests.md +++ b/Behind-the-scene-network-requests.md @@ -34,7 +34,7 @@ Also, the _behind-the-scene_ virtual tab is whitelisted by default, i.e. no filt To access the filtering settings for the behind-the-scene network requests is simple a matter of opening popup UI in the network request logger while the _"Behind the scene"_ entry is selected: -![Behind-the-scene popup](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/behind-the-scene-popup.gif)
The popup UI will be filled with the data of whatever tab is being currently inspected in the request logger. +![Behind-the-scene popup](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/behind-the-scene-popup.gif)
The popup UI will be filled with the settings/data of whatever tab is being currently inspected in the request logger. The picture above shows what happen when you navigate through Github: Github makes use of `navigator.sendBeacon()` to send data to Google Analytics, which results in the firing of behind-the-scene requests in Chromium browser.