-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 Rewards inline tipping functionality #34367
Remove Rewards inline tipping functionality #34367
Comments
Verified on macOS x64 13.x with
and
Verified test plan from brave/brave-site-specific-scripts#105 (comment). Nightly 1.62.x - PASSEDRewards not enabled, using dev component version 1.0.1127 - PASSED
Rewards enabled, using dev component version 1.0.1127 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
For comparison: Rewards not enabled, using (current) prod component version 1.0.527
Rewards enabled, using (current) prod component version 1.0.527
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
Release 1.60.x - PASSEDRewards not enabled, using dev component version 1.0.1127 - PASSED
Rewards enabled, using dev component version 1.0.1127 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
For comparison: Rewards not enabled, using (current) prod component version 1.0.527
Rewards enabled, using (current) prod component version 1.0.527
|
Verification PASSED on
And
1.62.x Clean profile NEW componentNightly 1.62.x_Rewards not enabled_PASSEDRewards not enabled, using dev component version 1.0.1127 - PASSED
Nightly 1.62.x_Rewards enabled_PASSEDRewards enabled, using dev component version 1.0.1127 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
1.62.x Clean profile OLD componentNightly 1.62.x_Rewards not enabled_PASSEDRewards not enabled, using prod component version 1.0.527 - PASSED
Nightly 1.62.x_Rewards enabled_PASSEDRewards enabled, using prod component version 1.0.527 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
1.60.x Clean profile OLD componentRelease 1.60.x_Rewards not enabled_PASSEDRewards not enabled, using prod component version 1.0.527 - PASSED
Release 1.60.x_Rewards enabled_PASSEDRewards enabled, using prod component version 1.0.527 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
1.60.x Clean profile NEW componentRelease 1.60.x_Rewards not enabled_PASSEDRewards not enabled, using dev component version 1.0.1127 - PASSED
Release 1.60.x_Rewards enabled_PASSEDRewards enabled, using dev component version 1.0.1127 - PASSED
Note - if you use a country that does not have auto contribution (ex. Japan, India), you will only have 7 "Greaselion" components in step 4. This is expected per discussions with Emerick as the additional ones are related to AC.
|
We updated the client to remove inline tipping functionality in #33783. While this removed the buttons and related settings from the client, the tipping scripts are still bundled with Greaselion. We should update Greaselion to remove those unused scripts.
The text was updated successfully, but these errors were encountered: