Brave-browser: Revert "navigator.deviceMemory"
Description
I recently changed my browser from Chrome to Brave. After that change, the Google's reCAPTCHA is annying every time I encounter it: after clicking on "I am not robot" there come a captcha to solve. The reCAPTCHA is never ending, and refusing to validate me. Especially the "click verify once there are none left" is the most annoying: the new pictures (after finding and clicking one) load within 15-30 seconds (so extreme low); which I absolutely don't understand. Previously, on Chrome, the new pictures loaded in 1 sec for the captchas like "click verify once there are none left".
What can I do? I don't want to revert to Chrome. I want to stick with Brave. But for me also the browsing expreience is important.
Steps to Reproduce
- Open a website which uses Google's reCAPTCHA.
- Click the checkbox "I am not robot".
- Try to solve the captcha.
Actual result:
Most of times I need to solve 10-20 captchas to proceed (previous captchas' solutions are also correct, but even so the Google keeps sending me the new and new captcha). So, solving one single captcha, like before with Chrome, is not anymore enough to proceed. And the "click verify once there are none left" captchas has an extrem high loading/unfading time for the new pictures.
This problem seems to be related to Brave, because that problem does not come with Chrome or Firefox browsers. (I tested them both)
Turning off the Brave shield does not help. It seems, Google tries to punish us, Brave users!
Expected result:
The reCAPTCHA should let me proceed after the checkbox "not robot" is checked. But even if not directly after, then at the latest when I solved the frist captcha.
Reproduces how often:
It comes every time, a reCAPTCHA is present on the website.
Brave version (brave://version info)
Used the 1.15.72 version on Debian Linux 10 (64-bit).
Version/Channel Information:
- Can you reproduce this issue with the current release? Yes.
- Can you reproduce this issue with the beta channel? Don't know.
- Can you reproduce this issue with the nightly channel? Don't know.
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? No.
- Does the issue resolve itself when disabling Brave Rewards? No.
- Is the issue reproducible on the latest version of Chrome? No. The reCAPTCHA with the Chrome works fine.
Miscellaneous Information:
bandi88
All 16 comments
we've gotten multiple reports of this and are investigating it. it's strange that this happens even with shields off.
diracdeltas
on 24 Oct 2020
@bandi88 Had a report that private window mode works, can you confirm?
ryanbr
on 24 Oct 2020
@bandi88 Had a report that private window mode works, can you confirm?
I tried it recently. Neither private window nor the private Tor window worked. reCAPTCHA was every time very problematic (like I wrote).
bandi88
on 24 Oct 2020
Same problem. I've found that switching to the audio version of the recaptcha often works.
To make sure it was specifically with Brave, I open up the following demo on Chrome, Safari, Firefox, Vivaldi - no issues: https://patrickhlauke.github.io/recaptcha/ (just a demo recaptcha site). All browsers passed immediately, whereas brave standard, brave private and brave tor all failed. Shields down, failed.
Audio recaptcha was fine.
ZachariahRosenberg
on 25 Oct 2020
Same problem. I've found that switching to the audio version of the recaptcha often works.
To make sure it was specifically with Brave, I open up the following demo on Chrome, Safari, Firefox, Vivaldi - no issues: https://patrickhlauke.github.io/recaptcha/ (just a demo recaptcha site). All browsers passed immediately, whereas brave standard, brave private and brave tor all failed. Shields down, failed.
Audio recaptcha was fine.
I have also problems with the audio reCAPTCHA with Brave: many times I have to solve 3-4 audio captchas, one is not enough for the Google's thing!
I hope, soon we will get a solution for that. Because reCAPTCHA is too much popular, almost all websites are using it (many of them invisibile, like Paypal for example).
bandi88
on 25 Oct 2020
MS edge on the left and Brave Beta on the right
snowbound
on 26 Oct 2020
Not sure if it contributes anything but I wasn't having this issue until I cleared my cache/cookies for a non-Brave issue I was troubleshooting. Once I cleared those, I began having the captcha issue, along with most sites not remembering I'm logged in.
ohmnominal
on 27 Oct 2020
Not sure if it contributes anything but I wasn't having this issue until I cleared my cache/cookies for a non-Brave issue I was troubleshooting. Once I cleared those, I began having the captcha issue, along with most sites not remembering I'm logged in.
I think, that Google introduced something recently, which leads Brave to fail. I started using Brave on 11st October 2020, but only had the issue first on 13rd October. I did not delete anything. But fresh installation of Brave is of course as cleared cache. :)
bandi88
on 27 Oct 2020
Had the same problem, it was finally resolved after allowing third party cookies and clearing all cookies.
mhidro
on 27 Oct 2020
Had the same problem, it was finally resolved after allowing third party cookies and clearing all cookies.
But is is not a final solution. In Firefox I can also use reCAPTCHA even in "strict mode" (where third-party cookies are not allowed). So, that issue seems related to the Brave browser.
bandi88
on 27 Oct 2020
Hello, I just wanted to add my comments. I am a new Brave user, migrating from Chrome. I see you are actively working on this issue, however Brave is unusable in its current state for a regular user, so I do hope it's been prioritized highly. CAPTCHA's are appearing for near-every website in both standard and private browsing mode, and they often require 5-10 correct solutions before allowing the user to proceed.
I have disabled all global shield settings, to no avail.
I hope you all are able to resolve this! Love the browser so far but, as I mentioned, this does make the browser unusable.
User5579
on 28 Oct 2020
I just tested this in Nightly - I am still getting sluggish load times on the photos, but the reCAPTCHA verified me after one round (instead of 10 or so like I was experiencing in production).
okidokiokami
on 29 Oct 2020
Unfortunately this didn't fix the reCAPTCHA issue but we'll still uplift https://github.com/brave/brave-core/pull/6968 & https://github.com/brave/brave-core/pull/6969 as per earlier discussions. @pilgrim-brave will implement farbling for navigator.deviceMemory via https://github.com/brave/brave-core/pull/6964.
However, @bsclifton and others are still looking into fixing the above. Seems like Nightly was fixed once C87 landed last night so we're looking into what could have possibly fixed the problem so we can uplift into the appropriate channels and release a hotfix ASAP.
kjozwiak
on 29 Oct 2020
Marked as release-notes/exclude since this didn't fix the issue (although, we could change the title to reverted navigator.deviceMemory.) New issue created with https://github.com/brave/brave-browser/issues/12359; 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
on 2 Nov 2020
@brave/legacy_qa because this didn't resolve the CAPTCHA issue, some of the cases mentioned via https://github.com/brave/brave-core/pull/6965#issue-510982570 are not valid for this particular issue. However, we'll need to check the following:
navigator.deviceMemoryshould return a number via the browser console rather thanundefined- https://antoinevastel.com/bots/ and confirm that everything is green as per the screenshot https://github.com/brave/brave-core/pull/6965#issue-510982570.
Also re-added release-notes/include as per conversations with @rebron & @bsclifton via Slack.
kjozwiak
on 2 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)
- verified that
navigator.deviceMemoryreturns a value rather thanundefineddue to the revert - verified that
Result of Fp-scannerunder https://antoinevastel.com/bots/ appears green
navigator.deviceMemory | Fp-scanner results
-------------------------------|---------------------------
| 
Verification passed on
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 1903 (Build 18362.1139)
verified that
navigator.deviceMemoryreturns a value rather thanundefineddue to the revert
verified that
Result of Fp-scannerunder https://antoinevastel.com/bots/ appears green
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 that
navigator.deviceMemoryreturns a value rather thanundefineddue to the revert
verified that
Result of Fp-scannerunder https://antoinevastel.com/bots/ appears green
kjozwiak
on 3 Nov 2020
Related issues
pitsi
路
3Comments
AlexCombas
路
3Comments
lansana
路
3Comments
fmarier
路
3Comments
simonhong
路
3Comments
Most helpful comment
Hello, I just wanted to add my comments. I am a new Brave user, migrating from Chrome. I see you are actively working on this issue, however Brave is unusable in its current state for a regular user, so I do hope it's been prioritized highly. CAPTCHA's are appearing for near-every website in both standard and private browsing mode, and they often require 5-10 correct solutions before allowing the user to proceed.
I have disabled all global shield settings, to no avail.
I hope you all are able to resolve this! Love the browser so far but, as I mentioned, this does make the browser unusable.