Just to clarify, I have all scripts blocked by default in the Brave site settings. Nevertheless, most webpages were virtually useless with script blocking turned on anyway, so I don't see much use for the BitWarden extension with script blocking turned Thanks for that research and intel. So it looks like that's the workaround: temporarily turn script blocking off, log in to BitWarden, then you can turn script blocking back on.Īlso noted BitWarden auto-fill did not work with script blocking turned on, although I could still cut-and-paste from the BitWarden vault into a webpage's user/password fields if I needed to. I noted that once I passed the captcha test and successfully logged in to BitWarden, I could turn script blocking back on and BitWarden still worked fine (since it didn't need the captcha test on subsequent logins). Also tried changing fingerprinting, tracking, and cookie settings to no effect, so it seems script blocking alone determines whether the captcha shows.

Repeated tests with script blocking alternating off/on, and the captcha either showed/didn't show, corresponding to the script blocking setting.

Tried to login to BitWarden and got no captcha, just like you said.Ĭhanged script blocking=off, restarted Brave, tried BitWarden, and the captcha appeared. I added no extensions other than BitWarden, and in Brave Shields set fingerprinting=strict, tracker blocking=aggressive, cookie blocking=cross site, and script blocking=on. Click to expand.I did a test with a portable install of Brave 1.34.80 with BitWarden 1.57.0 to see if I could replicate your results.

Bitwarden firefox