Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Request Button in-line in 2FA fields #103

Closed
3 tasks done
brandoningli opened this issue Sep 30, 2024 · 1 comment
Closed
3 tasks done

feat: Request Button in-line in 2FA fields #103

brandoningli opened this issue Sep 30, 2024 · 1 comment
Labels
Feature New feature or request

Comments

@brandoningli
Copy link

Feature description

Like how password managers often introduce a button on detected username and password fields, add a button to activate 2FAS from detected 2FA fields. Users should have the option to customize a list of selectors to target, and optionally contribute to a community list of selectors.
image

Motivation

While there is a keyboard shortcut option, I don't feel it's well known. The same can be said for the context menu option. Additionally, this would save users that choose to click to initiate 2FAS from potentially mousing quite far across the screen to press the extension button.

Combined with #85 , this would put 2FAS on par with some of the password manager provided experiences out there.

Acknowledgements

  • This issue is not a duplicate of an existing feature request.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@brandoningli brandoningli added the Feature New feature or request label Sep 30, 2024
@GrzegorzZajac000
Copy link
Member

Hi @brandoningli,

Thank you for submitting the feature request. We appreciate your suggestion; however, we have decided not to implement this feature for two main reasons. Firstly, users can already trigger the browser extension action in three different ways: keyboard shortcut, context menu, and the plugin button. Secondly, inputs for TOTP code do not have a distinct type, which would require the button to be displayed on nearly all inputs across all pages, leading to a potentially intrusive user experience, so we have made a conscious decision not to include this button within the inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants