github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-11 20:54:58 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android - Bitwarden does not recognize the username field on CFTS' site through Firefox. #1190

New Issue
Closed
opened 2025-11-26 22:41:37 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 22:41:37 -06:00
Owner
Copy Link

Originally created by @SergeantConfused on GitHub (Jan 23, 2021).

Describe the Bug

On Firefox, Bitwarden does not show the accessibility or autofill service overlay when you tap the username field, but does show the accessibility overlay when you tap the password field. When you autofill from the password field using the accessibility overlay, Bitwarden only autofills the password and leaves the username field blank.
Also on Firefox, inline autofill detects both the username and password fields, and autofills both when used from either field, but inline autofill is inconsistent in Firefox.
On Chrome, both inline and accessibility service detect both fields consistently, and Bitwarden autofills both fields.

Steps To Reproduce

  1. Open https://www.ctfs.com/content/dash/en/public/login.html in Firefox.
  2. Tap on the username field.

Expected Result

For the accessibility or autofill overlay to show up and to use it to autofill your credentials.

Actual Result

No overlay shows up, and you cannot autofill from the username field.

Screenshots or Videos

1
2

Environment

  • Device: Samsung Note 10+.
  • Operating system: Android 11.
  • Build Version: 2.8.0 (3349).
  • Is this a Beta release? N.

Additional Context

Inline autofill is not always presented as an option in Firefox, but always is in Chrome.
This has been reported to occur on an Android 7 device, as well. The screenshots are from this device.

Originally created by @SergeantConfused on GitHub (Jan 23, 2021). ## Describe the Bug On Firefox, Bitwarden does not show the accessibility or autofill service overlay when you tap the username field, but does show the accessibility overlay when you tap the password field. When you autofill from the password field using the accessibility overlay, Bitwarden only autofills the password and leaves the username field blank. Also on Firefox, inline autofill detects both the username and password fields, and autofills both when used from either field, but inline autofill is inconsistent in Firefox. On Chrome, both inline and accessibility service detect both fields consistently, and Bitwarden autofills both fields. ## Steps To Reproduce 1. Open https://www.ctfs.com/content/dash/en/public/login.html in Firefox. 2. Tap on the username field. ## Expected Result For the accessibility or autofill overlay to show up and to use it to autofill your credentials. ## Actual Result No overlay shows up, and you cannot autofill from the username field. ## Screenshots or Videos ![1](https://user-images.githubusercontent.com/73389600/105611718-98492800-5dbf-11eb-8b7c-ffb403e89144.png) ![2](https://user-images.githubusercontent.com/73389600/105611719-997a5500-5dbf-11eb-8599-d61d288c99ad.png) ## Environment - Device: Samsung Note 10+. - Operating system: Android 11. - Build Version: 2.8.0 (3349). - Is this a Beta release? N. ## Additional Context Inline autofill is not always presented as an option in Firefox, but always is in Chrome. This has been reported to occur on an Android 7 device, as well. The screenshots are from this device.
GiteaMirror commented 2025-11-26 22:41:38 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Apr 29, 2021):

Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.

@eliykat commented on GitHub (Apr 29, 2021): Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.
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
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#1190
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?