From 98b015c1011699429ced4c390135a78ad537b881 Mon Sep 17 00:00:00 2001 From: Brian Zelip Date: Sat, 30 Dec 2017 10:39:32 -0500 Subject: [PATCH] Three minor grammar edits. --- Disable-hyperlink-auditing-beacon.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Disable-hyperlink-auditing-beacon.md b/Disable-hyperlink-auditing-beacon.md index 908607a..886ecc4 100644 --- a/Disable-hyperlink-auditing-beacon.md +++ b/Disable-hyperlink-auditing-beacon.md @@ -4,10 +4,10 @@ See [_"Hyperlink-Auditing aka `` and Beacon aka `navigator.sendBeacon()` ### Chromium-based browsers -For those browsers, the network requests fired as a result of calling `navigator.sendBeacon()` are send as [behind-the-scene](https://github.com/gorhill/uBlock/wiki/Behind-the-scene-network-requests) network requests. +For those browsers, the network requests fired as a result of calling `navigator.sendBeacon()` are sent as [behind-the-scene](https://github.com/gorhill/uBlock/wiki/Behind-the-scene-network-requests) network requests. #### Caveats for browsers based on Chromium version 48 or less -Network requests created as a result of web pages using `navigator.sendBeacon()` **will not be blocked** when the setting _"Disable hyperlink auditing/beacon"_ is checked. This is a limitation of the chrome API prior to v49, as network request fired as a result of calling `navigator.sendBeacon()` are reported as the generic type `other` by the browser. +Network requests created as a result of web pages using `navigator.sendBeacon()` **will not be blocked** when the setting _"Disable hyperlink auditing/beacon"_ is checked. This is a limitation of the chrome API prior to v49, as network requests fired as a result of calling `navigator.sendBeacon()` are reported as the generic type `other` by the browser. -The [webRequest API](https://developer.chrome.com/extensions/webRequest) was extended in Chromium 49 to support new request types, and thus the settings works fine for any browser based on Chromium 49 or higher, as there is now a specific network request type, `ping`, which uBO normalizes to `beacon` -- and hence can now filter correctly. \ No newline at end of file +The [webRequest API](https://developer.chrome.com/extensions/webRequest) was extended in Chromium 49 to support new request types, and thus the setting works fine for any browser based on Chromium 49 or higher, as there is now a specific network request type, `ping`, which uBO normalizes to `beacon` -- and hence can now filter correctly. \ No newline at end of file