1P6b - minor bug - field editing on a new entry

amjbrown

When I create a new login it appears that I can enter text to the left of the field names (username, password etc.). Haven't tried committing it as I don't want to suffer the potential fallout!

When tabbing through the fields this is the default location. For example having entered username, if I don't press TAB twice to get to the password field, I end up on the left of it.

---

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

mohamedosman

Haven't tried committing it as I don't want to suffer the potential fallout!

@amjbrown there's no known issues with editing the field title, so you shouldn't worry about breaking things. And, if you do make a mistake while editing, you can go right back and edit it :)

amjbrown

Ah - so this is not a bug, but rather the ability to edit the field name?

In which case I would expect it to highlight ready to be typed over when tabbing into it? Currently you add characters to the front of the field name, And it is a curious thing to edit by default working through that tab order of fields - normally you would add a username then add a password, rather than always offering the field name edit capability?

Of course I only discovered this because you can't currently add a logon directly from the browser extension in the 6 beta for Windows :)

mohamedosman

it is a curious thing to edit by default working through that tab order of fields - normally you would add a username then add a password, rather than always offering the field name edit capability?

Ah, I see your point here @amjbrown, but you typically aren't able to edit the field title **at all* when entering this type of data, so it makes sense to skip it when tabbing through a similar form. But with 1Password we give you the power to edit the field title so that you can have more control over how your data is organized.

Of course I only discovered this because you can't currently add a logon directly from the browser extension in the 6 beta for Windows

We're working on that ;)

dorellang

Ah, I see your point here @amjbrown, but you typically aren't able to edit the field title **at all* when entering this type of data, so it makes sense to skip it when tabbing through a similar form. But with 1Password we give you the power to edit the field title so that you can have more control over how your data is organized.

To tell the truth, I find this behavior confusing, unintuitive and just feels glitchy. As for me, I won't be using this feature, and IMHO most users won't be using it very often. So maybe I think that there should be a checkbox that says "Make field titles editable" (unticked by default) that enables the feature, else it behaves like a plain old form. I know that this may bloat the interface a bit, but I understand that this feature might be interesting for some users; it's just that having it on by default doesn't feel all right (for me at least).

Another UI suggestion is that the underline below the field contents is too light so it's hard to see (at least in my crappy laptop screen), so it took me a while to realize that you could name each item in a vault (since there is no field title before at the right of the name).

That's it, take this only as a graint of salt.

MikeT

Hi @dorellang,

I just want to follow up here with a few clarifications.

It is a bug in 1Password 6 Beta where it lets you edit known "protected" template field labels. For an example, the username/password/ website are protected in the Logins item, they're not supposed to be editable and when you tab, it should skip them. As soon as the app is updated to respect "protected" labels, the tabbing experience will improve at the same time.

The field labels are only editable for custom fields and for 'non-protected' field titles.

ref: #357

Another UI suggestion is that the underline below the field contents is too light so it's hard to see (at least in my crappy laptop screen), so it took me a while to realize that you could name each item in a vault (since there is no field title before at the right of the name).

I'll pass it on to our design team to look at this, I can see why it is difficult to see.