Strange behaviour in "All Fields" section of logins

Edwin

I've never really used the "All Fields" section of the logins screen before, but when I look at entries in my 1Password created some time ago, I see the following:



[img]http://photos.smugmug.com/photos/1119359160_yGh7G-O.jpg[/img]



But for new entries (created since about mid-November), the login entry looks like this:



[img]http://photos.smugmug.com/photos/1119359173_iNqpH-O.jpg[/img]



You can see that the "All Fields" section does not title the entries correctly as "username" and "password", as is the case with the first screenshot.



If you edit the password entry for these two examples, you see the following:



[img]http://photos.smugmug.com/photos/1119359168_isMCv-O.jpg[/img]



[img]http://photos.smugmug.com/photos/1119359192_MUeuu-O.jpg[/img]



In the existing entry (for Adobe), the "All Fields" section shows the two fields, labelled correctly as a username and password. For the new test entry, there are three fields displayed. One contains the username, one contains the password but there is an extra third field which is blank. Also, none of the fields have the correct field names (although the ticks are in the correct place on the right side).



Now this doesn't really bother me, except for when I sync with my iPhone. On the iPhone, the "All Fields" section is displayed at the top of the page and is the bit I always look at. You can see in the screenshot below that the entry looks a bit messy as there is an extra blank line and no labels on the left hand side (just blank space). The password is also displayed in the normal font (not the nice font you normally use for displaying passwords on the iPhone app). Old entries still look fine, and display the labels "username" and "password" and do not have this blank line.



[img]http://photos.smugmug.com/photos/1119359200_JBwCr-O.jpg[/img]



As I said, this has only started occurring for password entries created from about mid-November. All entries created previously are fine. Is this the correct behaviour or is this a bug?

khad

I was not able to find a login form on the BBC main page (http://www.bbc.co.uk/). Have I missed it?

Edwin

There probably isn't one, but I don't think that is the problem. I'm creating these logins directly in the main 1Password application on the Mac. That's how I have always created my logins and how I created the Adobe example one.



In the past, 1Password populated the "all fields" bit nicely with just the username and password, but now it seems 1Password is adding a blank extra field by default and not adding a title to the username/password sections.



I wouldn't mind, except that it is the "all fields" section which is displayed more prominently on the iPhone app, so when I open a password entry there is a blank line and blank space on the left when I view the username/password.

khad

We recommend allowing 1Password to automatically (and even manually) save logins from [i]within your browser[/i]. Creating them manually in the application is left as an exercise for the reader. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />



I'm not sure that anything has changed in 1Password, but I'll make a note of it.

Edwin

Ok thanks for the recommendation. I have always created my logins manually though and never had any problems!



From my point of view, something in 1Password has changed because my workflow has been the same for ages. It's not a major problem, just a minor annoyance which I thought I would mention.

khad

My apologies. I forgot that this [i]was[/i] changed from using placeholder field names ("username," "password") and field values ("your username," "your password") to having blank values since outside of 1Password's browser integration there is no way to know what the [i]actual[/i] field names or values for any given web page might be. Some sites use "email" or "userid" rather than "username." Some use "passcode" or "pin" rather than "password." We decided to leave the fields blank to more accurately reflect the nature of a newly created empty login.



Again, if you save a login from within the browser 1Password will [b]automatically[/b] grab the field names along with their values from the actual code of the web page and populate them accordingly in the new login item. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Cheers!

Mezzanine

[quote name='Edwin' timestamp='1291848488' post='17206']

There probably isn't one, but I don't think that is the problem. I'm creating these logins directly in the main 1Password application on the Mac. That's how I have always created my logins and how I created the Adobe example one.



In the past, 1Password populated the "all fields" bit nicely with just the username and password, but now it seems 1Password is adding a blank extra field by default and not adding a title to the username/password sections.



I wouldn't mind, except that it is the "all fields" section which is displayed more prominently on the iPhone app, so when I open a password entry there is a blank line and blank space on the left when I view the username/password.

[/quote]



Just to make sure you haven't overlooked this, you can manually add/edit the field names and remove blank entries...



In fact, when creating login's within the app, it's better to add info directly into the "all fields" section and then assign specific fields to the main username and password entries by using the tickboxes on the right.



Regards,

Mezzanine.

khad

Thanks for the tip, Mezzanine. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

Edwin

[quote name='khad' timestamp='1291927801' post='17261']

My apologies. I forgot that this [i]was[/i] changed from using placeholder field names ("username," "password") and field values ("your username," "your password") to having blank values since outside of 1Password's browser integration there is no way to know what the [i]actual[/i] field names or values for any given web page might be. Some sites use "email" or "userid" rather than "username." Some use "passcode" or "pin" rather than "password." We decided to leave the fields blank to more accurately reflect the nature of a newly created empty login.



Again, if you save a login from within the browser 1Password will [b]automatically[/b] grab the field names along with their values from the actual code of the web page and populate them accordingly in the new login item. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Cheers!

[/quote]



Thanks, this all makes sense.



I guess my only other point would be to question why a blank field is created for every new login item (as shown in the screenshots above). Maybe this isn't the case if you allow the browser to create the login item automatically, but if you manually create the login item within 1Password you get the field for the username, another one for the password, and also a blank field.



I appreciate that it is recommended to allow the browser to create the login items for you though. Although I've been using 1Password for quite a while now, the software I was using before to manage my passwords required you to create login items manually and I guess I am stuck in my ways!



[quote name='Mezzanine' timestamp='1291930147' post='17264']

Just to make sure you haven't overlooked this, you can manually add/edit the field names and remove blank entries...



In fact, when creating login's within the app, it's better to add info directly into the "all fields" section and then assign specific fields to the main username and password entries by using the tickboxes on the right.



Regards,

Mezzanine.

[/quote]



Yes, I have been using these options to tidy up my logins, thanks!

khad

[quote]I guess my only other point would be to question why a blank field is created for every new login item (as shown in the screenshots above). Maybe this isn't the case if you allow the browser to create the login item automatically, but if you manually create the login item within 1Password you get the field for the username, another one for the password, and also a blank field.[/quote]

Sorry I didn't mention it in my post, but that particular aspect should be resolved in an update. It is on our radar. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



[quote]I appreciate that it is recommended to allow the browser to create the login items for you though. Although I've been using 1Password for quite a while now, the software I was using before to manage my passwords required you to create login items manually and I guess I am stuck in my ways![/quote]

I know the feeling! I won't get into it, but I still have some old Windows-using habits from years ago that I am still trying to shake. Fortunately, 1Password was the first password manager I used — before ever working for Agile. I never could wrap my head around how anyone could stand all the copying/pasting/application-switching/etc. that other password managers require. Maybe I'm just lazy. (Shh. Don't tell the boss.) <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol:' />



The best part is that you can just browse the web normally and 1Password will automatically prompt you to save your passwords. You don't really have to remember to do anything differently so much as just let it happen. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />