Brave-browser: CAPTCHA being shown all the time in Brave

Created on 28 Oct 2020  路  5Comments  路  Source: brave/brave-browser

Test plan

See https://github.com/brave/brave-core/pull/6993

Original issue description

Have you searched for similar issues? Yes. #1677 is the closest thing I found but I think that as specific to tor and sightly different.

Description

I'm finding too many captch notifications on freelancing sites such as Fiverr and Upwork either when opening multiple tabs of the same site at once or after opening new tabs of the same site after a while on the same site.
It can be a problem if you've right-click and open links on the site to view later and you don't even realise that the captch has been created and even if you comply with captcha and finish it, it shows that you've completed it with a green tick, however, the site become permanently stuck and you've lost the page that you were on refreshing the page doesn't help as you don't even know what that specific tab was and we should even have to refresh. Brave is supposed to reduce the amount of time and save time but quite often it doesn't. I've noticed more and more that I'm wasting time with Brave just trying to get sites to work or refreshing sites or fixing tab issues and we should have to.

Furthermore, turning Shields off and on doesn't help after the fact. Sites simply become stuck with Shields on or off.

Steps to Reproduce

I don't know exactly how to reproduce it as it occurs randomly but a lot of the times when I have around a dozen or more tabs of the same site open either at once or randomly.

Actual result:

Screenshot_20201010_200530

Screenshot_20201027_174556 2

Screenshot_20201027_154223

Expected result:

I'll let you figure it out )

Reproduces how often:

At least once every time I'm on the site and that's not to say just on one tab but in every tab that I have opened of that site, so it completely disrupts the workflow.

Brave version (brave://version info)

Version 1.15.76 Chromium: 86.0.4240.111 (Official Build) (64-bit) (openSuse)

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? No.
  • Does the issue resolve itself when disabling Brave Rewards? I didn't try.
  • Is the issue reproducible on the latest version of Chrome? This is most likely a Brave specific issue.
OAndroid ODesktop QA Pass - Android ARM QA Pass - Android Tab QA Pass - Android x86 QA Pass-Linux QA Pass-Win64 QA Pass-macOS QYes prioritP1 release-noteinclude
Source
picture NumDeP

Most helpful comment

I may have said this before but the stat on Brave's dashboard which shows the number of hours saved is simply untrue if you factor in the amount of time a user wastes with issues similar to this.

I know I have no right to tell you what to do but this issue has been such an annoyance for so long I'd greatly appreciate if the team figured out a way to fix issues like this without us users having to do anything on our side, otherwise we'd be just wasting more time and disrupt important workflow.

Thanks )

picture NumDeP on 28 Oct 2020
👍3 😄2 👎1

All 5 comments

I may have said this before but the stat on Brave's dashboard which shows the number of hours saved is simply untrue if you factor in the amount of time a user wastes with issues similar to this.

I know I have no right to tell you what to do but this issue has been such an annoyance for so long I'd greatly appreciate if the team figured out a way to fix issues like this without us users having to do anything on our side, otherwise we'd be just wasting more time and disrupt important workflow.

Thanks )

NumDeP picture NumDeP on 28 Oct 2020
👍3 😄2 👎1

Thanks for reporting - we have been looking into this and have attempted some fixes, no luck yet

Previously reported with https://github.com/brave/brave-browser/issues/12289

bsclifton picture bsclifton on 28 Oct 2020

Fixed in master (1.18.x) with https://github.com/brave/brave-core/pull/6554 and fixed in 1.16 with https://github.com/brave/brave-core/pull/6993. 1.17.x will get the fix when Chromium 87 is uplifted

bsclifton picture bsclifton on 2 Nov 2020

@jonathansampson @pes10k @bsclifton and a few others have confirmed that the above change which was included in 1.16.71 CR: 86.0.4240.111 have improved things 馃憤

kjozwiak picture kjozwiak on 3 Nov 2020

Verification PASSED on macOS 10.15.7 x64 using the following build:

Brave | 1.16.71 Chromium: 86.0.4240.111聽(Official Build)聽(x86_64)
-- | --
Revision | b8c36128a06ebad76af51591bfec980224db5522-refs/branch-heads/4240@{#1290}
OS | macOS Version 10.15.7 (Build 19H2)

Tried running through https://levalet.com/en/customer/account/login/ as per the STR/Case outlined via https://github.com/brave/brave-core/pull/6993#issue-512847061 but kept running into the following error:

You cannot proceed with such operation, your reCaptcha reputation is too low.

However, Chrome seems to be running onto the same issue so considering the above as a pass as the other websites worked plus several confirmations as per https://github.com/brave/brave-browser/issues/12359#issuecomment-720594323.

@LaurenWags once you've checked on Mojave, you can label as QA/Pass. @fmarier @bsclifton let me know if you disagree with the above.

Verification PASSED on macOS 10.14.6 x64 using the following build:

Brave | 1.16.72 Chromium: 86.0.4240.183聽(Official Build)聽(x86_64)
-- | --
Revision | 0b568b034b8f7994697cb341eeca5979b84151cc-refs/branch-heads/4240@{#1374}
OS | macOS Version 10.14.6 (Build 18G6032)
  • ensured that logging into https://www.paypal.com didn't produce/display a reCAPTCHA (I don't have accounts with https://www.bell.ca, https://www.rogers.com to try those)

Ran into same error above with STR/Case outlined via https://github.com/brave/brave-core/pull/6993#issue-512847061.

Verification passed on

Brave | 1.16.72 Chromium: 86.0.4240.183聽(Official Build)聽(64-bit)
-- | --
Revision | 0b568b034b8f7994697cb341eeca5979b84151cc-refs/branch-heads/4240@{#1374}
OS | Ubuntu 18.04 LTS

Verified test plan from https://github.com/brave/brave-core/pull/6993#issue-512847061

Verification PASSED on Win 10 x64 using the following build:

Brave | 1.16.72 Chromium: 86.0.4240.183 (Official Build) (64-bit)
--- | ---
Revision | 0b568b034b8f7994697cb341eeca5979b84151cc-refs/branch-heads/4240@{#1374}
OS | Windows 10 OS Version 2004 (Build 19041.572)

Verification PASSED on Mint 19.1 x64 using the following build:

Brave | 1.16.72 Chromium: 86.0.4240.183 (Official Build) (64-bit)
--- | ---
Revision | 0b568b034b8f7994697cb341eeca5979b84151cc-refs/branch-heads/4240@{#1374}
OS | Linux

Verification passed on Asus Zenfone (x86) with Android 6.0 running 1.16.71 Bravex86.apk

  • Confirmed on a clean install of 1.16.71 that logging in to paypal.com didn't produce/display a reCAPTCHA
  • On upgrade (from 1.16.68), a reCAPTCHA was displayed on initial login, but subsequent logins were fine and did not show reCAPTCHA.

Verification PASSED on Samsung S10+ with Android 10 running 1.16.73 CR 86.0.4240.185

Note: I did receive a reCAPTCHA on PayPal when I was in desktop mode but resolved in one try which is a lot better compared to what was happening on previous versions. Tried multiple times and only received it once.

Verification passed on Brave 1.16.74 on Samsung Galaxy Tab S5e (Android 9.0)

Reproduced on 1.16.70

Verified test plan from https://github.com/brave/brave-core/pull/6993#issue-512847061

kjozwiak picture kjozwiak on 3 Nov 2020
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

AlexeyBarabash picture AlexeyBarabash  路  3Comments
fmarier picture fmarier  路  3Comments
hollons picture hollons  路  3Comments
bsclifton picture bsclifton  路  3Comments
jonathansampson picture jonathansampson  路  3Comments