Comparing entry web form data = scrolling through 4 "1-inch high pages"? [under consideration]

steven

Hopefully, I'm just missing something - any other view options here, besides exporting to csv?

How do I display an entry's web form data in standard (non-pop-up) format??

I need to consolidate/purge "multiple logins for the same site," so I must compare the fields. I edit an entry, then click "show web form," and scroll through 4 "1-inch high pages," and what...? Taking 4 mini-screenshots as I go, to compare with 4 other little mini-screenshots from another entry?

Holy Schnikeys, look at all that whitespace, like freshly fallen snow. Fill it up with words! :-D

Thanks for reading.

Steven

sjk

Hi, @steven. Thanks for reporting this.

Right now the Show web form details popover window is limited to displaying eight fields at a time. Scrolling usually isn't necessary since most Login items have fewer fields saved there. We are considering other ways to display this, e.g. similar to the disclosure triangle method in 1P3.

Maybe there's a way you can make this easier moving forward? In your shopaddonics.com example image are all fields being used to fill a web form? Are there any fields that could be migrated to custom fields? And are all six custcheck4 fields necessary or could redundant ones be deleted?

You're right about the whitespace there. :)

steven

Hey, @oversoul

I appreciate the response :-)

We are considering other ways to display this, e.g. similar to the disclosure triangle method in 1P3.

• A disclosure triangle sounds like a great compromise - less shiny/pretty than a button, but if user can actually see his data, then cool.
• A "Show all form data" checkbox in an "Advanced..." prefs section would work, too, if losing the button makes you guys cringe. The checkbox could revert to "unchecked" on startup, eliminating the chance that grandma gets confused after grandson has cleaned up her database & left without unchecking "Show all." (I'm not a programmer, I know that may not be feasible, but the older table view, with field name popups, while obviously too busy for primetime, was the pinnacle of the fast cleanup.)
• Considering the difficulties inherent in making all this data both accessible (which is kind of necessary when editing/pruning data), and easy on the eyes (which is great for everyday use) I've always loved AB's design decisions. On both Mac & iOS, always trying to push the ugly data away from my eyeballs, supplanting it with "site thumbs" etc. So nice. Big icons and all, my typical reaction to the 1pw GUI is just "oh... of course that's how it should be."

In your shopaddonics.com example image are all fields being used to fill a web form? Are there any fields that could be migrated to custom fields? And are all six custcheck4 fields necessary or could redundant ones be deleted?

Thanks - but I'm unsure, conceptually, if using custom fields will make up for "not being able to examine & compare the saved data" to put in a custom field, yeah?

(I know 1pw can't prevent the 12-15 lines of junk put in many web forms by @badformdesigner, and I'm okay that it's my job to clean things up - but the current form display implementation has essentially shut down my tried & true cleanup process, since the 1passwd days.

Correct me if I'm wrong, but in practice, the limitations of the pop-up are like a memory test when cleaning up multiple entries for a particular site (if the # of entries, fields, etc, below seems high, I'll say "yes, higher than the average." But not the highest, and even if the tiny pop-up has to have two pages, and there's only two entries to compare, it's still kind of silly):
1. for 3-6 different 1pw entries,
2. select the entry on the left
3. cursor over to the "web form" button
4. click button and then scroll up and down the 3-4 iPhone-sized pages of pop-up data
5. memorize 12 to 15 lines of practically contextless form garbage from the site,
6. cursor back to the entries list and click the next entry
7. Repeat.

I can't imagine my usage is fringe, but welcome any advice so long as:
a) no data loss
b) no mandatory manual editing per login save

I'm hoping for a "Hey, idiot, just push the 'fix' button - it's been there for the last 3 point releases" :-)

---

FWIW, how I end up w/ multiple entries:

The reality of multiple entries

1. I sign up for a web account
   1. enter all my info for the account.
   2. I will usually save "the sign up form" in 1pw,
   3. (because I need to have that data (secret questions, address, username, the whole thing))
2. Quite often (due to the site's bad form implementation, I'm sure),
   1. when I return to the site to log in via the regular login screen (versus the sign-up page),
   2. the saved account data will fill the form incorrectly.
   3. This is most typically "filling username instead of email," or vice versa.

Periodic Cleanup, when the GUI was not a pop-up

The problem is, like all of us I'm sure, I simply don't have the time at that very moment to fiddle with the housework required to clean up the 1password entry.

1. I don't want to lose my data (now spread over several 1pw entries)
   1. usually "the sign-up entry" and "the entry that actually works for logging in,"
   2. often a couple more.
      1. an alternate or new login page
      2. maybe acct login used for forum login
2. I periodically launch 1password and "cleanup/consolidate" the multiple entries that always arise from these kind of login data discrepancies.

Unknown

This content has been removed.

Megan

Hi @steven and @AndrewParker,

Thanks so much for adding such detailed feedback here. I'm sorry that I don't have any immediate solutions for you here, but I will be sure that the developers here about your use case. You bring up some good points

As far as multiple entries go, we've recently updated our 'Save new Login' pop-up to allow you to 'Update an Existing Login' instead, which should help to curb those multiples at least a little. I know that it doesn't help for right now, but hopefully our future selves will have an easier time keeping things organized because of this. :)

Mike Althaus

I agree that the web form details should not be a pop up window, data should be visible in the expansive data area.

sjk

Along with the ability to add new fields to web form details, overall improvements to their visibility and editing are under consideration,