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

[PR #4511] [MERGED] PM-16474 Adding custom field issues when another text field holds focus #5005

New Issue
Closed
opened 2025-11-26 23:52:45 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:52:45 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/4511
Author: @dseverns-livefront
Created: 12/30/2024
Status: ✅ Merged
Merged: 1/7/2025
Merged by: @dseverns-livefront

Base: main ← Head: PM-16474-custom-field-adding-issue

📝 Commits (1)

  • 7d92303 PM-16474 clear device focus from any other item in add/edit list when a new custom field is being added to help maintain scroll position

📊 Changes

1 file changed (+7 additions, -2 deletions)

View changed files

📝 app/src/main/java/com/x8bit/bitwarden/ui/vault/feature/addedit/VaultAddEditCustomFieldsButton.kt (+7 -2)

📄 Description

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-16474

📔 Objective

  • When the dialog for naming the custom field is displayed it seems to re-trigger the focus on the outer textfield which causes the list to scroll back to that field in the background consistently and sometimes causes the dialog to dismiss before the user can interact.
  • We now clear any other held focus when the user click the button to create the new custom field.

📸 Screenshots

Before
https://github.com/user-attachments/assets/049cb29f-618b-466e-9ab8-a13903e66367
After
https://github.com/user-attachments/assets/709f9d7b-d9ce-4405-966c-fe57f760bda8

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/4511 **Author:** [@dseverns-livefront](https://github.com/dseverns-livefront) **Created:** 12/30/2024 **Status:** ✅ Merged **Merged:** 1/7/2025 **Merged by:** [@dseverns-livefront](https://github.com/dseverns-livefront) **Base:** `main` ← **Head:** `PM-16474-custom-field-adding-issue` --- ### 📝 Commits (1) - [`7d92303`](https://github.com/bitwarden/android/commit/7d923030e51da2f44b93f8b1a96b4bce7b8568a0) PM-16474 clear device focus from any other item in add/edit list when a new custom field is being added to help maintain scroll position ### 📊 Changes **1 file changed** (+7 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/java/com/x8bit/bitwarden/ui/vault/feature/addedit/VaultAddEditCustomFieldsButton.kt` (+7 -2) </details> ### 📄 Description ## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-16474 <!-- Paste the link to the Jira or GitHub issue or otherwise describe / point to where this change is coming from. --> ## 📔 Objective - When the dialog for naming the custom field is displayed it seems to re-trigger the focus on the outer textfield which causes the list to scroll back to that field in the background consistently and sometimes causes the dialog to dismiss before the user can interact. - We now clear any other held focus when the user click the button to create the new custom field. <!-- Describe what the purpose of this PR is, for example what bug you're fixing or new feature you're adding. --> ## 📸 Screenshots | Before | |--------| | https://github.com/user-attachments/assets/049cb29f-618b-466e-9ab8-a13903e66367 | | After | |--------| | https://github.com/user-attachments/assets/709f9d7b-d9ce-4405-966c-fe57f760bda8 | <!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. --> ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-26 23:52:45 -06:00
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 pull-request
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#5005
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?