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

LastPass thinks every field in the IMS is a password / credential field #375

Open
kimballa opened this issue Sep 13, 2022 · 2 comments
Open

Comments

@kimballa
Copy link

A couple of times during the event I used my phone + wifi to type an incident report from Berlin rather than go down to HQ to type it up.

A frustrating element of this is that for whatever reason of how fields in the incident report form are (or are not) tagged with HTML attributes or CSS, LastPass thinks that every field (e.g., incident report summary line) on the IMS -- including the big textarea -- is a username field, and focusing each field repeatedly prompts me to unlock lastpass to use a saved credential.

I'm not sure why exactly LastPass was so zealous about wanting to fill out the form fields, but according to their support site (https://support.lastpass.com/help/how-do-i-prevent-fields-from-being-filled-automatically) the fix is trivial, just add the 'data-lpignore'=true attribute to the various <input> and <textarea> tags in the Incident editor and Incident Report editor pages.

@wsanchez
Copy link
Member

I'm not going to application LastPass-specific markup all over IMS… That sounds a lot like a LastPass configuration issue.

@kimballa
Copy link
Author

Regarding the config issue... I would tend to agree. The mobile app also doesn't have a ton of configuration options. I could blacklist the entire site from my phone but that's about it.

(I also wonder if it's because the <input> and <textarea> tags don't have a name attribute? It's generally pretty good about calling the correct form fields with few if any false positives, so there is something a bit hinky with the html on this site that is tripping it up.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants