github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #6283] [PM-29915] Removal of autofill compatibility mode is a regression #8445

New Issue
Closed
opened 2026-04-11 01:45:13 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-11 01:45:13 -05:00
Owner
Copy Link

Originally created by @knadsady on GitHub (Dec 17, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6283

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.
Originally created by @knadsady on GitHub (Dec 17, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6283 ### 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.
GiteaMirror added the app:password-managerbug labels 2026-04-11 01:45:14 -05:00
GiteaMirror commented 2026-04-11 01:45:16 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 18, 2025):

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

<!-- gh-comment-id:3667640840 --> @bitwarden-bot commented on GitHub (Dec 18, 2025): Thank you for your report! We've added this to our internal board for review. ID: [PM-29915](https://bitwarden.atlassian.net/browse/PM-29915) [PM-29915]: https://bitwarden.atlassian.net/browse/PM-29915?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-11 01:45:16 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 18, 2025):

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"...

Image
<!-- gh-comment-id:3667680416 --> @pamperer562580892423 commented on GitHub (Dec 18, 2025): 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"... <img width="913" height="515" alt="Image" src="https://github.com/user-attachments/assets/1e102d71-99a4-415f-9fe1-f998cc3e1310" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#8445
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?