1744241 - Cannot login to Asus account site, possible captcha code blockage

Status: RESOLVED WORKSFORME

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[Tony Davis]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

Went to site: https://account.asus.com/
Input my normal valid email and password, login box just stalls.

Actual results:

Login box stalls, login does not complate. If I refresh the page, I can see a captcha box appear for a very short time, then it dissapears. This looks like a race condition between the WEBGL code, and the JS driving the captcha or ReCaptcha. Not sure if there is any interaction/interference with the Password Manager?

Expected results:

Normal login should occur, as it used to do, prior to some updates. NOTE: this DOES work on Chrome, but I do NOT see any captcha codes.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Toolkit::Password Manager' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Sergey Galich [:serg]]

:tihuang this feels related to bug 1686956, can you take a look and move to Privacy: Anti-Tracking if needed?

Comment 3

[Tim Huang[:timhuang] [PTO 10/19 ~ 11/3]]

Tom, do we have an existing webcompat issue with Recaptcha?

Comment 4

[Thomas Wisniewski [:twisniewski]]

Not to my knowledge. From the sound of things, if it's a race condition then it may be an intermittent issue that some users experience more than others, but usually those are website bugs (yes, even in big services like Recaptcha). So this is definitely worth investigating as a webcompat issue to confirm where the race condition actually lies, and whether the bug is with all sites using Recaptha or just under certain circumstances.

Comment 5

[Tony Davis]

FYI: I read the related BUG 1686956 with interest, as it seems there are lots of sporadic reports of similar issues with ReCaptcha functions or code.

There was a comment in that, stating that since an update to FF94, the problem could not be reproduced. However, I can confirm that the issue with my logging into the ASUS account, STILL fails under FF95.02 (and still works OK under Chrome).

If you need be to run any debug stuff, or console/code inspects, please let me know.

Comment 6

[Tony Davis]

FYI: I just tested the issue with FF Nightly 98.0a1 and it still fails in the same way.

Comment 7

[Tim Huang[:timhuang] [PTO 10/19 ~ 11/3]]

Hi Tony,

Would you be able to provide your troubleshooting information on the about:support page? This could help us to diagnose the problem. Thanks.

Comment 8

[Tony Davis]

Attachment: FF96_ABOUT_SUPPORT.txt

FYI: updated to FF96 the other day, and took an about:support TXT file for another bug, so here it is now for this one.

Comment 9

[Tim Huang[:timhuang] [PTO 10/19 ~ 11/3]]

From the troubleshooting info, I can see that you have installed addons for adblocking. Would you be able to try the troubleshoot mode to see if the issue still exists?

Comment 10

[Tony Davis]

FYI: Thanks for the suggestion. I DID try that, and observed exactly the same condition (initial "flash" of the ReCaptcha code graphic for a fraction of a second, then when attempting to use my valid credentials, nothing happens - as presumably the form is waiting for me to respond with the Captcha code as well, which is hidden, and unrendered.)

NOTE: I have taken some console error log diagnostics during this login, and can see this interesting error line:
"Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.
modernizr-2.5.3.min.js:4:3612"

Researching using my limited knowledge of JSCRIPT, reveals that this modernizr-2.5.3.min.js is very old (probably from 2012 or so), and the current version is 3.50, so I imagine it is missing on YEARS of Firefox feature checks.

I have a couple of small log files in 2 word documents, that I will attach in a minute, in case you think that, or some of the other errors, might be the cause of the ReCaptcha bug or timing issue.

Comment 11

[Tony Davis]

Attachment: ERROR_LOG_FROM_ASUS_LOGIN.docx

ERROR_LOG_FROM_ASUS_LOGIN.docx

Comment 12

[Tony Davis]

Attachment: CONSOLE LOG FROM ASUS LOGIN.docx

CONSOLE LOG FROM ASUS LOGIN.docx

Comment 13

[Tony Davis]

I just tried an interesting test, for this login issue. I used the "forget site" option, that gets rid of ALL cookie, supercookie, and stored data info, and form data, for the ASUS site.

I was able to log in ONE TIME perfectly OK, BUT when I logged out, and attempted to log back in, I was back to the original problem. I am not sure if that helps in any way, or hints at where to concentrate on the testing/diagnostic effort for this issue. Please advise.

Comment 14

[Tony Davis]

FYI:
I tested this again today after I had contacted ASUS & raised a ticket with them (as I was suspicious of their down-level modernizr-2.5.3.min.js), probably around 2 weeks ago now.

It did seem to work much more consistently, and I do NOT get any login stalls, and no ReCapcha "flash".

The only anomaly, is that after a successful login, the LockWise P/W manager does a drop-down asking to update the entry, as it thinks there is no user name or email address. Checking the LockWise passwords showed a proper and complete entry for that same site. When I DID add the same and correct email address for that account, I then got TWO password entry records, one with the favicon.ico, and one without, with the SAME URL entry.

I suspect this is a site compatibility issue, caused by a form or detection bug, but I often get this with sites that have "odd" password entry forms. Maybe it is one of those "multiple login entry" forms that cause issues with detections (ongoing enhancements for this in FF I understand).

I can BUG that seperately if you feel it is worthwhile.
NOTE: I also now on FF 97.01, so cannot be sure if this was fixed between FF94 and FF97, or if Asus site developers have fixed their older JS scripts.
Please set this BUG status to whatever is now appropriate.

Comment 15

[Tim Huang[:timhuang] [PTO 10/19 ~ 11/3]]

Thanks for reporting back. I think you can file another bug for the password manager issue and I will close this bug, feel free to reopen this if you encountered the same issue again. Really appreciate your help here.