Forum Discussion

williakz's avatar
williakz
Dedicated Contributor
4 years ago

1Password interfering with Amex FICO Simulator

Amex's MyCredit Guide site has a credit score simulator function where a user can enter various credit events to see what effect they would have on their FICO number. Unfortunately, 1Password sees some but not all of these "what-if" fields as fillable and places its logo in the selected field, thereby obscuring and interfering with user entry of desired data. How does one tell 1Password "Hands Off!" these particular fields, this page, the site, etc.? Thanks in advance for any and all assistance. Chrome on Mac (latest production versions of all OS and application software).

Link (Simulator has a menu tab on main MyCredit Guide page):
https://www.mycreditguide.americanexpress.com

P.S. I realize the issue in this specific case is trivial. I posted it to learn if and how 1Password can be instructed to skip processing such fields in case similar behavior occurs in more substantive contexts.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

13 Replies

  • Anonymous's avatar
    Anonymous

    Hey williakz ,

    1Password uses a lot of indicators on every page to determine what type of page it is (a login page? A sign-up? A payment page?), and then suggests relevant actions accordingly.

    It uses clues that are found throughout the page and the HTML code behind the scenes to determine in which fields it should show up in and what each field does. For example, if a field is called "Credit card number", 1Password will most likely determine it needs to show up and suggest autofilling your credit card.

    Sometimes this can be incorrect if you are on a very long page with a bunch of fields that look like they are fillable for 1Password but in fact are fields that should be manually filled by the user. For example, if you're on a real-estate website and you need to enter a certain address to look at a property, 1Password might show up in it and suggest autofilling your address/identity item, but that would be irrelevant.

    It sounds like this is happening on this website, which I couldn't access as I don't have an account, and when trying to sign up with bogus info it said that there's no data with the info I provided. However I don't think it is really relevant as the explanation above is most likely correct in this particular instance.

    We are always working on improving 1Password's autofilling abilities and logic, but that is a never-ending uphill battle as every website is built and designed differently, and most of them do not adhere to any specific standard :)

    If you'd like us to take a look at that webpage where things didn't work as expected, please send us the page's structure like so:

    1. Get to the page where 1Password showed up in the wrong places.
    2. Right-click the extension's icon on the top right corner of the browser and select "Help" -> "Collect Page Structure".
    3. Send us the downloaded file to mailto:support+x@1password.com along with a short description and a couple of screenshots showing in which fields it showed up and why it shouldn't show up in them.

    That would allow us to improve 1Password on that particular page and perhaps on others like it :+1:

  • williakz's avatar
    williakz
    Dedicated Contributor

    Thanks, @ag_ana, that did the trick for Amex's credit score Simulator page. Can you tell me if there is a field-level "hiding" function in case a particular page has both fields I want 1Password to process along with ones I don't?

    Also, I'd appreciate it if you or another tech could take a look at the Simulator page and tell me why some fields appear to be misinterpreted by 1Password while others very similar in content and function are properly processed (left alone). Thanks again.

  • Anonymous's avatar
    Anonymous

    williakz:

    How does one tell 1Password "Hands Off!" these particular fields, this page, the site, etc.?

    P.S. I realize the issue in this specific case is trivial. I posted it to learn if and how 1Password can be instructed to skip processing such fields in case similar behavior occurs in more substantive contexts.

    You can use the Hide on this page button in the 1Password inline menu, when you click on it: