![]() ![]() Since the browser doesn't wait for Privacy Badger when restoring tabs, it's possible for requests to go through before Privacy Badger is ready to deal with them. Privacy Badger takes a little time to initialize itself. If you see this happen when you restart the browser in a profile configured to reopen previously open tabs, you're probably running into #1845. ![]() These 3 are both websocket requests with a status of 101 if that may be of use. Also the 2 requests to never finish apparently and stall while downloading as well as 1 request from. Even disabling cache in Devtools does not seem to change the results. What's curious is that Privacy badger does seem to correctly block all, spclient.wg. and requests but not all the requests of. Privacy badger does seem to allow the various scdn domains you talked about even with Privacy badger on. Curiously enough maybe it's some sort of caching or something but even after completely relaunching the browser Privacy badger still allows the Spotify widget to load and only seems to replace it after a few seconds. ![]() I have turned off brave shields as well in order to keep it simple. 105 (Official Build) (64-bit) and Windows 10 Version 20H2 and OS build 19042.867. Trying this on my own system using Brave: Version 1.22.70 Chromium. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |