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

Recaptcha page says "browser not supported" #22

Closed
balcy opened this Issue Aug 24, 2018 · 7 comments

Comments

Projects
6 participants
@balcy
Copy link
Collaborator

balcy commented Aug 24, 2018

recaptcha did not accept browser-ng (states that it is not a supported browser)
there is an example page to test recaptcha:
https://patrickhlauke.github.io/recaptcha/

It seems to be interpret the user agent and block the browser because of that.
We can try another user agent string, but should avoid side effects like pages directing users to the Play Store (because they think the browser is android) or wrong rendering of pages...

@balcy

This comment has been minimized.

Copy link
Collaborator

balcy commented Sep 22, 2018

@balcy

This comment has been minimized.

Copy link
Collaborator

balcy commented Oct 11, 2018

it is really a pity that one cannot reach companies directly to report issues nowadays. There are several chromium related posts in the "support" forum, one Ubuntu Touch related one of 2016.
https://groups.google.com/forum/m/#!searchin/recaptcha/chromium/recaptcha/e_QdyJR36_k
I think it would be better not using recaptcha at all, but you cannot decide as user :[
Maybe we can make it so that we present the Chrome user agent to recaptcha servers only, and keep Chromium generally.

@dobey

This comment has been minimized.

Copy link

dobey commented Oct 15, 2018

Odd. I've been using Chromium exclusively for years on my Ubuntu systems, and never once had an issue with recaptcha due to the user agent. So very odd that changing it to Chrome here would have any effect. Perhaps it's more related to the fact that we stick "Android" into the user agent as a means of tricking web sites to serve up mobile versions, and perhaps Google does require Chrome in that case?

@Stefano0101

This comment has been minimized.

Copy link

Stefano0101 commented Oct 15, 2018

Yes, this issue is confirmed on Meizu Pro 5. 16/04/OTA-5/stable.

@Billdemoncho

This comment has been minimized.

Copy link

Billdemoncho commented Oct 16, 2018

I confirm the same problem on my meizu pro 5 in 16.04 dev and updated.

screenshot20181016_234417243

@NeoTheThird NeoTheThird referenced this issue Nov 1, 2018

Closed

Fix papercuts in Morph-Browser #914

4 of 6 tasks complete

@balcy balcy closed this Nov 3, 2018

@UniversalSuperBox UniversalSuperBox added this to To do in OTA-6 QA Tracker via automation Nov 23, 2018

@ferrettim

This comment has been minimized.

Copy link

ferrettim commented Nov 27, 2018

device:Nexus 5
channel: RC 2018-W48
issue solved. Unable to reproduce using recaptcha test linked above.

@tjrhodes

This comment has been minimized.

Copy link

tjrhodes commented Nov 27, 2018

Device: FP2
System Build: 2018-W48

Issue solved, the test link loaded the vanilla recaptcha widget and it was functional.

As mentioned above though it is odd, Chromium on Ubuntu desktop has no such problems, is it confirmed to be related to putting android in the request headers? Can anyone test with chromium on android?

@UniversalSuperBox UniversalSuperBox moved this from To do to Accepted in OTA-6 QA Tracker Nov 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment