Update to v1.21.73 breaks some extensions

Description

Many users are reporting broken extensions that were previously working just fine after updating to version 1.21.73. Note that most of these extensions seem to have some relation to passwords and/or the browser reading/writing data from the device to the browser. Additionally, users are reporting that the extensions are still working as intended in Chrome/Edge/Other Chromium browsers. cc @rebron @jumde @ryanbr

Brave version (brave://version info)

Version 1.21.73 Chromium: 89.0.4389.72 (Official Build) (64-bit)

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? No
• Does the issue resolve itself when disabling Brave Rewards? No
• Is the issue reproducible on the latest version of Chrome? No

Miscellaneous Information:

User threads: https://community.brave.com/t/brave-version-1-21-73-chromium-89-0-4389-72-on-mac-breaks-enpass/212242/9 https://community.brave.com/t/avast-password-down-after-1-21-brave-update/212277 https://community.brave.com/t/xdm-doesnt-work-after-updating-brave-browser/212260

Images:

[Varusal]

Solution:

1. brave://adblock
2. add this line

Now the extensions works perfectly fine.

[Creyox]

Solution:

1. brave://adblock
2. add this line

Now the extensions works perfectly fine.

I was googling “Brave whitelist” yesterday and couldn’t find this for the life of me. Are there no side-effects with the rule?

Edit: Not working here, even after a restart.

Try using 127.0.0.1 instead of localhost, this seems to work for me