Skip to main content
October 1, 2026

Taking Autofill to the Next Level: User-Guided Field Mapping & Transparency

  • October 1, 2026
  • 0 replies
  • 1 view

1. Feature Needed: User-Assisted Autofill Field Selection & Transparency Indicator To resolve issues where autofill fails due to complex HTML, shadow DOMs, or non-standard pop-up/iframe structures, please consider implementing a dynamic manual target selection tool:

  • Manual Target Selection: Allow users to right-click or use a browser extension tool (e.g., "Set as Username/Password Field") to manually map an HTML element to a stored credentials entry for future auto-detection.

  • Autofill Status / Failure Transparency: If the extension detects an input form or pop-up window but cannot reliably parse the target fields, display an explicit status indicator (e.g., "Form detected, but autofill fields could not be mapped") rather than failing silently.

2. Bug Report: Inconsistent Autofill Execution on the Same URL I am experiencing intermittent autofill behavior on an identical URL without any variation in the link:

  • Symptom: On the exact same page, the extension successfully detects and populates the login fields on some visits, but fails entirely on others without user intervention or structure changes.

  • Expected Behavior: Consistent field recognition and autofill across sessions on identical domain paths and DOM structures.

  • Troubleshooting Steps Already Taken: Cleared extension cache, verified URL matching rules (exact host/path matching), and confirmed no conflicting third-party form-fill extensions are active.

Environment Details:

  • Browser & Version: Chrome 

  • OS: macOS