-
Notifications
You must be signed in to change notification settings - Fork 2.6k
CAPTCHA not being displayed within rewards panel when initiated via brave://rewards
#22447
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
Comments
Reproduced the issue in
|
The above requires |
Verification
Test Case 1: Verified CAPTCHA displayed when initiated from brave://rewards after dismissing initial
Note: Below are regression test cases to test all flows. Test Case 2: Verified
Test Case 3: Complete onboarding from brave://rewards and click
Test Case 4: Launch onboarding from
Test Case 5: Launch onboarding from
|
Verification passed on
Test Case 1: Verified CAPTCHA displayed when initiated from brave://rewards after dismissing initial
Note: Below are regression test cases to test all flows. Test Case 2: Verified
Test Case 3: Complete onboarding from brave://rewards and click
Test Case 4: Launch onboarding from
Test Case 5: Launch onboarding from
|
Description
CAPTCHA isn't being launched via the rewards panel when initiated using
brave://rewards
. Once you've dismissed the initialClaim Rewads
button/modal that appears within the panel, you don't be able to claim your rewards viabrave://settings
due to the CAPTCHA not appearing in the panel.Steps to Reproduce
--rewards=staging=true --brave-ads-staging
X
to dismiss theClaim Rewards
modalbrave://rewards
and attempt to claim the reward/grantActual result:
broken.mp4
Expected result:
working.mp4
Reproduces how often:
100% reproducible when using the STR/Cases outlined above.
Brave version (brave://version info)
Version/Channel Information:
No
No
(need to wait for a1.39.x
BETA to check)Yes
Other Additional Information:
N/A
N/A
N/A
Miscellaneous Information:
CCing @emerick @Miyayes @LaurenWags @zenparsing
The text was updated successfully, but these errors were encountered: