[PM-29915] Removal of autofill compatibility mode is a regression

[knadsady]

Steps To Reproduce

Autofill compatibility mode resolved #6107. But then it was removed as of #6191 which has resulted in a regression and the original bug filed in #6107 to resurface. Whatever changes in #6191 that were supposed to resolve the issue have actually reintroduced the problem. The "automatic" fix is not working, resulting in the same behavior described in #6107.

Expected Result

See #6107.

Actual Result

See #6107.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.12.0 (21003)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

• Device: OnePlus 13
• Android Version: 15, kernel 6.6.30-android15-8-gb5f0c188ea2a-ab12656338-4k
• Browser: Samsung Internet 29.0.0.59

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-29915

[pamperer562580892423]

Another user here.

And at least on Edge, I don't see that... (the compatibility mode was mainly (only?) needed for Edge, Opera and Samsung Internet)

BTW, I would not jump to conclusions early. As I understood it, the compatibility mode is more or less on by default now (with 2025.12.0), so probably only the toggle was removed - and then, it could be a new bug and maybe is not caused by the "removal"...