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

URI input fields in Login items are not formatted best for entering URLs #301

New Issue
Closed
opened 2025-11-07 08:34:39 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-07 08:34:39 -06:00
Owner
Copy Link

Originally created by @jmot205 on GitHub (Nov 8, 2018).

This is for the Android app.

I'm not sure of the official terminology, but basically this relates to typing in the numbered URI fields in a Login item - URI 1, URI2, etc. When typing with a keyboard that has auto formatting options (I'm currently using SwiftKey, but this isn't specific to that keyboard), when I type the period to put in a .com, the keyboard applies autoformatting and puts in a space after the period and starts with a new capital letter, like typing a normal sentence.

This autoformatting doesn't happen when typing directly in the URL bar of e.g. Chrome or Firefox, so I think it has to do with how the text input field is set up (e.g. like how some fields can be set up so that the keyboard knows it's a numerical input, and so the numpad part of the keyboard comes up by default - I'm guessing there's one typically used for URL fields, so that the keyboard knows not to apply any automatic formatting to what's typed in that field.)

Originally created by @jmot205 on GitHub (Nov 8, 2018). This is for the Android app. I'm not sure of the official terminology, but basically this relates to typing in the numbered URI fields in a Login item - URI 1, URI2, etc. When typing with a keyboard that has auto formatting options (I'm currently using SwiftKey, but this isn't specific to that keyboard), when I type the period to put in a .com, the keyboard applies autoformatting and puts in a space after the period and starts with a new capital letter, like typing a normal sentence. This autoformatting doesn't happen when typing directly in the URL bar of e.g. Chrome or Firefox, so I think it has to do with how the text input field is set up (e.g. like how some fields can be set up so that the keyboard knows it's a numerical input, and so the numpad part of the keyboard comes up by default - I'm guessing there's one typically used for URL fields, so that the keyboard knows not to apply any automatic formatting to what's typed in that field.)
GiteaMirror commented 2025-11-07 08:34:39 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 8, 2018):

The field is set to keyboard type "Url" with DisableAutocapitalize=true and Autocorrect=false . Does this happen whenever you try using another keyboard?

@kspearrin commented on GitHub (Nov 8, 2018): The field is set to keyboard type "Url" with DisableAutocapitalize=true and Autocorrect=false . Does this happen whenever you try using another keyboard?
GiteaMirror commented 2025-11-07 08:34:39 -06:00
Author
Owner
Copy Link

@jmot205 commented on GitHub (Nov 8, 2018):

Ah right, those definitely sound like options that should prevent this happening :/

Yeah, this behaviour also happens when I use Fleksy, for example. I've just now also tried with Gboard, and it is behaving as expected (i.e. no auto formatting) with Gboard.

One thing I also noticed when comparing the keyboard inputs just now is that when clicking into an empty URI input field, SwiftKey and Fleksy start with a capital letter, whereas Gboard starts with lower case, which kind of matches how the first two still apply autoformatting and the latter doesn't.

@jmot205 commented on GitHub (Nov 8, 2018): Ah right, those definitely sound like options that should prevent this happening :/ Yeah, this behaviour also happens when I use Fleksy, for example. I've just now also tried with Gboard, and it is behaving as expected (i.e. no auto formatting) with Gboard. One thing I also noticed when comparing the keyboard inputs just now is that when clicking into an empty URI input field, SwiftKey and Fleksy start with a capital letter, whereas Gboard starts with lower case, which kind of matches how the first two still apply autoformatting and the latter doesn't.
GiteaMirror commented 2025-11-07 08:34:40 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 9, 2018):

I am not sure why the keyboards are not respecting the input field flags. It sounds like a bug with the keyboard itself.

@kspearrin commented on GitHub (Nov 9, 2018): I am not sure why the keyboards are not respecting the input field flags. It sounds like a bug with the keyboard itself.
GiteaMirror commented 2025-11-07 08:34:40 -06:00
Author
Owner
Copy Link

@jmot205 commented on GitHub (Nov 9, 2018):

Yeah, I originally asked because I thought maybe the flags weren't set for the URI field, and that's why it would act normally in Chrome and Firefox URL fields. But given that you've got the flags in there, it seems fair enough that it's just a bug in SwiftKey and Fleksy to not respect the flags.

@jmot205 commented on GitHub (Nov 9, 2018): Yeah, I originally asked because I thought maybe the flags weren't set for the URI field, and that's why it would act normally in Chrome and Firefox URL fields. But given that you've got the flags in there, it seems fair enough that it's just a bug in SwiftKey and Fleksy to not respect the flags.
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#301
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?