Can not see Buster button in CAPTCHA window

[jnobile91]

System

• OS name: Windows
• OS version: 10
• Browser name: Chrome
• Browser version: 100.0.4896.60

Extension

• Extension version: 1.3.1
• User input simulation: Can't find this setting

Bug description I am unable to view the Buster button on the CAPTCHA window. The extension appears to be loaded correctly, but there is no visible button to solve the CAPTCHA Screenshot here: https://imgur.com/8z1K01B

Logs Browser:

Nothing in console.

[dessant]

I have just tested with the same browser and the extension button is at the bottom of the challenge popup. Have you refreshed the page after installing the extension?

[jnobile91]

Yes, I have tried to refresh. Still unable to see any Buster button in the challenge window.

[dessant]

Were the extension settings changed to limit site access, or is there a different extension installed that could interfere? It's also possible that Google is testing a change, but that should have caused more bug reports by now.

[jnobile91]

I disabled all other extensions (Only had Google Drive active) and still receiving the same issue.

[jnobile91]

I also just had a few coworkers test this using the same version of Chrome and Buster. Looks like they are also having the same issue. I know Chrome recently updated to version 100 a few days ago. Is it possible that this version is preventing it from loading correctly?

[dessant]

I've made the previous test with Chrome 100. Have you all installed the extension for the first time and it just didn't work, or did it stop working only after the latest Chrome update? Are these company devices running some network or browser monitoring solution?

[jnobile91]

I just installed the extension and attempted to get this working on the existing version of Chrome (v100). I don't believe there is any browser monitoring software running, but I can confirm with IT perhaps. I'm not able to view any error log either, since I don't believe it is initializing at all.

Thank you so much for your help to this point. Sincerely appreciate it!

[BenjaminDaSilva]

Same issue here on Win10 / Chromium Edge 100.0.1185.39

[jnobile91]

Any suggestions?

[BenjaminDaSilva]

So it's working here in Google Chrome 100.0.4896.127 (Official Build) (32-bit) now - for wti.ai (managed) apparently the quota is used up, but I've created a free IBM Watson speech to text account and with that it works just fine.

The "Solve" Button is still not shown in Chromium Edge 100.0.1185.50 (Official Build) (64-Bit) though. Maybe a 32bit vs 64bit thing?

[dessant]

If it isn't a browser bug, one possibility could be that the challenge is served from a different host that is not known to the content script. Please open the challenge popup, then paste this in the page console (Ctrl+Shift+J) and share the output:

document.querySelectorAll('iframe').forEach(item => console.log(item.src))

Also check if the target element of the extension button is reachable. Switch the current frame in the console from top to the frame name that ends with (bframe) while the challenge popup is still open, then run this command:

document.querySelector('#recaptcha-help-button')

You could also go to chrome://extensions/?id=mpbjkejclgfgadiemmefgebjfooflfhl, turn on Developer mode and Collect errors, then restart the browser, open the challenge popup and revisit the extension page. Any error in the background script should be shown in the console when you click on Inspect views src/background/index.html.

[BenjaminDaSilva]

[BenjaminDaSilva]

The demo above is maybe not the best example, also doesn't work in Chrome. The following one works in chrome but not in Chromium Edge: Edge: Chrome:

https://recaptcha-demo.appspot.com/recaptcha-v2-checkbox-explicit.php

[tjengbudi]

hello, my problem is related to this, however i can show. but i cannot click it with my python program.

shadow-root <= what is this used for? any chance to ger rid about this?

if not how to access it by xpath? css_selector? i cannot found by id

[dessant]

@tjengbudi, don't use this extension in your scripts.

[dessant]

I can't reproduce the issue after several attempts since the bug report was opened, if someone finds a way to reproduce the issue and get some error logs, please let me know.