-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "Allow contributions for videos" setting in Auto-Contribute because it does not work #27990
Comments
note, #13394 still open - so likely this setting controlled the display of all media publishers (twitter, GH, etc) in the AC list, not just video ones. |
This setting will control whether or not a "media publisher" on one of the Greaselion-enabled sites will be added to the AC table as the user navigates. It currently does not filter out or remove any existing entries in the AC tables. After GL was implemented, all media sites were changed to be routed through the save "video" AC path for AC measurement purposes. That's the explanation behind #13394. @Miyayes What do you think the follow-up for this should be? |
Unabl eto reproduce the issue on |
We will be removing this toggle as it does not work and does not add much value. |
@brave/qa-team when testing this also check upgrade scenarios (setting enabled, setting disabled, AC enabled, AC disabled, etc) |
Verification PASSED on Clean profile
Upgrade profile
|
Description
Previously, the "Allow contributions for videos" auto contribution setting would control whether media publishers could be shown in the auto contribution table.
In 1.47.x, 1.48.x, 1.49.x this setting no longer seems to work. Unsure when it stopped working.
Steps to Reproduce
Actual result:
Expected result:
Videos (Jonathan Sampson on Youtube in above examples) should not be listed in AC panel
Reproduces how often:
easily
Desktop Brave version:
1.47.x, 1.48.x, 1.49.x
Android Device details:
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @Miyayes
The text was updated successfully, but these errors were encountered: