brave-browser: Some of Brave's Default Shields settings breaking extensions
Description
I realize that this may seem obvious since this was a common issue with the pre-installed extensions in Browser-Laptop but given that Brave-Core allows for all Extensions, this problem pops up much more often and supporting/advising users on how to address the issue is slightly problematic.
Examples:
1 - Evernote Web Clipper
This extension installs without issue but breaks after attempting to sign-in to Evernote account. Sign-in is still registered/successful, but the extension cannot be used and you’re presented with the following error:
2 - Diigo Web Capture - Capture and Annotate
This extension works very much in the same way as Evernote. Installs fine and even further, account sign-in works properly. However, when attempting to use the extension (for instance, clicking “Add a Bookmark”, the extension displays as seen here:
The loading wheel in the top right spins infinitely. Selecting “save” closes the extension but does not actually save the content.
Both of these issues are resolved by changing Brave’s default Shields settings - specifically changing the Cookie Control option to Allow all cookies. Once switched, these extensions behave as expected.
This occurs on both Dev and Beta versions, with or without fresh install and with or without additional extensions installed.
Steps to Reproduce
(Covered above but will simplify)
- Install Evernote Web Clipper extension
- Sign into your Evernote account via extension or website
- Attempt to use any function of Evernote Web Clipper
Actual result:
Function is not performed, alert message to make sure cookies are allowed is displayed.
Expected result:
Evernote function executes
Reproduces how often:
Always
Brave version (chrome://version info)
Beta - Version 0.55.10 Chromium: 70.0.3538.22 (Official Build) beta (64-bit) Dev - Version 0.56.1 Chromium: 70.0.3538.22 (Official Build) dev (64-bit)
Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? Yes
- Does it reproduce on browser-laptop? No/ NA
Website problems only:
- Does the issue resolve itself when disabling Brave Shields? Not site-specific Shields
- Is the issue reproducible on the latest version of Chrome? No
Additional Information
Initial reports: https://community.brave.com/t/diigo-annotate-and-capture/33859 https://community.brave.com/t/evernote-web-clipper-extension/33648/4
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 7
- Comments: 37 (12 by maintainers)
Links to this issue
Commits related to this issue
- Disable shields for extensions The reasoning is they have APIs to do much worse tracking than our shields would protect them from. Users install them knowing they will have elevated permissions Fix ... — committed to brave/brave-core by bbondy 6 years ago
- Disable shields for extensions The reasoning is they have APIs to do much worse tracking than our shields would protect them from. Users install them knowing they will have elevated permissions Fix ... — committed to brave/brave-core by bbondy 6 years ago
- Release notes for 0.57.x Fix #2401 — committed to brave/brave-browser by kjozwiak 6 years ago
+1 on the Google Keep extension
Todoist extension doesn’t work when shields are up. Version 0.70.12 Chromium: 76.0.3809.72 (Official Build) nightly (64-bit)
Has this been fixed? It is not allowing me to use the Evernote Clipper Extension, saying I need to allow 3rd party cookies and even if I chose to allow all cookies in Braves settings nothing changes.
Please post new issues, we keep 1 issue per landed area of code unless it is reverted. Thank you!
+1 for Mixmax (https://www.reddit.com/r/brave_browser/comments/9rbgc2/what_settings_need_to_be_changed_to_allow_the/)
Gmail integration does not work (tested in 0.58.9), “Allow all cookies” fixes it in the meantime.
Agreed, once we start migrating users in
0.57.x, a lot more folks will be running into this issue when they start using extensions. We’ll probably be seeing a lot more +1’s being added. @bbondy can we get someone to look at this and see if it’s possible to fix for0.57.xbefore we migrate?@bbondy @rebron @kjozwiak this one needs to be fixed and uplifted to 57 if possible. There’s an increasing number of complains about extension being broken because of default global shields settings.
+1 from Community with Soapbox extension from Wistia https://community.brave.com/t/soapbox-from-wistia-cant-log-in/34306?u=eljuno