Alexei

Hello! As a workaround, I'll add `clients2.google.com` to Privacy Badger's yellowlist tomorrow. Once that's done, Privacy Badger will let requests to `clients2.google.com` through but without access to cookies.

Thanks @pixkk for the report! I just added these two domains to the workaround list. You should get the latest list automatically within the next 24 hours. To force an...

Looks we break logging into [Line](https://chromewebstore.google.com/detail/line/ophjlpahpchlmihnnnihgmmeilfjmjjc): - https://g0v.social/@fankt/112640950947868007 - https://ckhung0-blogspot-com.translate.goog/2024/06/chrome-line-privacy-badger.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp

This should be fixed in Chrome as of Chrome version 128. Thank you @kzar!

Reload works with web-ext 8.6.0 and `--arg="--disable-features=DisableLoadExtensionCommandLineSwitch"` and manually "keeping" and re-enabling the reload manager extension. However the manual keep/re-enable is pretty annoying if you want to frequently relaunch for...

Try reproducing with MV3 Privacy Badger: https://github.com/EFForg/privacybadger/tree/mv3-chrome

Thank you for the workarounds! However, if it's indeed DNR, I don't think `web-ext` users with DNR extensions should individually have to discover and work around this problem.

Yeah agreed on all points (I don't like the `_metadata` directory either!), and thank you for the super quick response!!

>With the latest web-ext version, the mechanism to reload extensions is the same as (re)installing an extension, which appears to trigger the full (DNR) initialization. Does this mean something about...

>If you'd like to learn more about the motivation and differences Thanks, I looked at the linked issues, but I don't see an explanation of the differences between reloading with...