How do you save a form? [Fixed in 3.7b9]

gpc

I'm using the latest non-beta version of 1password (Version 3.7.0 (build 31083)), the current Safari extension (3.7.b7). Snow Leopard, Safari 5.1.

The help page that comes up when I click on '?" in 1password's preferences/logins indicates:





[quote]

Login Options



Enable Autosave of Logins in browser



When the Autosave preference is enabled, every form with a password field that 1Password does not already have a record for will be saved as a new Login. If you have multiple logins for the same site that use the same password, you will need to [b]manually select Save Login from the 1Password toolbar icon in your web browser.[/b][/quote]





??? I cannot find any way to bring up a "save login" option by clicking on the 1P toolbar icon in Safari. Holding down Option or Shift or Command or combinations of them seems to make no difference. Holding down Ctrl makes it a right-click, which brings up either Safari's customize toolbar options (clicking on the "1P" button) or the option to "reload" (if the 1password control panel is already open from a click on "1P")



I know in the past week or so I've used the procedure to resave a login, based on instructions either in this forum or in the online help pages. It does not seem to be possible any more with 3.7.0/extension 3.7.b7.

tzs

Am I missing something? I don't see a way in Safari with the new extension to manually create a new login for a page. The only way seems to be to actually submit and hope that 1Password detects it as something new and asks if you want to save it.



On Chrome, whose extension is superficially similar, there is a "save" button below the list of already saved items for the site.

MikeT

Hi gpc,



I’m sorry for the confusion. We had to remove the option to manually save a login in the current extension version. We’re working on bringing it back as soon as possible. I don’t have any timeframe but it should be within the next few days.

MikeT

[quote name='tzs' timestamp='1312230947' post='35743']

Am I missing something? I don't see a way in Safari with the new extension to manually create a new login for a page. The only way seems to be to actually submit and hope that 1Password detects it as something new and asks if you want to save it.



On Chrome, whose extension is superficially similar, there is a "save" button below the list of already saved items for the site.

[/quote]Hi tzs,



I merged your topic with this one because it is very similar. Please read my last post about the missing ’save login’ option. The short answer is that we’ll working on bringing it back asap in Safari 5.1.

gpc

[quote name='MikeT' timestamp='1312235312' post='35769']Hi gpc,



I’m sorry for the confusion. We had to remove the option to manually save a login in the current extension version. We’re working on bringing it back as soon as possible. I don’t have any timeframe but it should be within the next few days.

[/quote]



OK. Thanks for the reply. FYI, still missing in 3.7b8.

roustem

[quote name='gpc' timestamp='1312246976' post='35820']

OK. Thanks for the reply. FYI, still missing in 3.7b8.

[/quote]



Please update to 3.7b9. At the moment you will need to:



1. Manually enter the login information on the current page.

2. Select "+" button:



[img]https://img.skitch.com/20110802-1tr4wgbmhbssggryathjp2rij9.png[/img]

gpc

Good, I see it there. And I see there's an "edit" button now when I click on an existing login's arrow (at the right of the blue highlight).



There are some glitches with the interface. The "notes" field has a resize handle at the lower right that I can pull beyond the boundary of the 1P panel. (I tried to insert an image here but I've given that up as hopeless.)



And, [s]as you can see,[/s] the font used for the login title is too big for this small panel. The panel as a whole could use a resize handle. (I'm running Snow Leopard; maybe Lion handles window resizing differently?) Or the panel just needs to jump out to a larger area while adding/editing a login/viewing details. (Did I just suggest making the panel larger? Cue the hordes with torches and pitchforks.... But seriously, this is about usability.)



There's also something inconsistent about whether the "+" responds. [s]I did the above screen captures by going to "edit" my existing agile.ws login because[/s] On the agile.ws page, the "+" did not respond for adding a login[s] on that page[/s]. On another site, the "+" worked properly, but one of my existing logins for the page would not display details for editing/saving (no response on clicking on the login's blue arrow).

brenty

[quote name='gpc' timestamp='1312264261' post='35907']

(Did I just suggest making the panel larger? Cue the hordes with torches and pitchforks.... But seriously, this is about usability.)

[/quote]



ROFL. Honestly, you are the only person I have ever seen that says "make it bigger!" Thank you for that. I think the main thing to keep in mind (especially in light of the redesign) is that we are not afraid to iterate and make changes.



I am afraid the screenshots didn't work out there. Good catch on the Notes resize, though! If you can give us more information privately so that we can produce the unresponsive + button, that would be great. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

gpc

Well, when the user just wants to login to a site, having the panel pop up etc is very intrusive and clunky compared to the old system, and having a big ugly panel pop up is even worse. For that, making the panel smaller helps, a bit.



Once the user is editing details of a login in the extension, it no longer makes sense to try to cram it all into a postage stamp. At that point the panel is more like a working window and needs to be large enough to comfortably accommodate what the user is doing.



The + doesn't respond for me on these forum.agile.ws pages. If it works on agile.ws for your testers, have them try a few different sites.

[quote name='brenty' timestamp='1312264872' post='35909']

ROFL. Honestly, you are the only person I have ever seen that says "make it bigger!" Thank you for that. I think the main thing to keep in mind (especially in light of the redesign) is that we are not afraid to iterate and make changes.



I am afraid the screenshots didn't work out there. Good catch on the Notes resize, though! If you can give us more information privately so that we can produce the unresponsive + button, that would be great. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

[/quote]

MikeT

Hi gpc,



We made a change so that for any sites with a single Login, it won’t bring up the panel, it’ll just directly fill in and submit it for you. If there are more than one, you do need to select which item to fill in, so we optimized the design to be smaller and faster for that.



We’re working within the extension APIs provided by Apple for Safari, I’m not sure there is a way to resize the window dynamically yet for the editing section, but we will definitely look into seeing if we can do this. Thank you for the suggestion, it’s a great idea.



As for the manual save, thanks for bringing up the forums as an example. I can definitely confirm that it is not working for me the first time. What I did notice was that if you refresh the page, it’ll then work. Try that.



Many of our users do test several sites and majority of them works. You can try Facebook.com now and see how it was supposed to work. I just informed our devs about this and they'll look into this.

brenty

[quote name='gpc' timestamp='1312267307' post='35915']

Well, when the user just wants to login to a site, having the panel pop up etc is very intrusive and clunky compared to the old system, and having a big ugly panel pop up is even worse. For that, making the panel smaller helps, a bit.



Once the user is editing details of a login in the extension, it no longer makes sense to try to cram it all into a postage stamp. At that point the panel is more like a working window and needs to be large enough to comfortably accommodate what the user is doing.



The + doesn't respond for me on these forum.agile.ws pages. If it works on agile.ws for your testers, have them try a few different sites.



[/quote]



It actually never occurred to me to test sites I use for work, since our customers aren't using most of them. Oddly enough though, I didn't have any trouble saving a new login here -- even a duplicate of my existing one.



In regards to the window size: It isn't set in stone; we will have to tweak it over time and figure out what is the best fit. We still have features to add at this point, so it makes sense to wait a bit. I rarely even see the panel, though. For the vast majority of sites, I have a single Login item and ⌘\ gets me in. For the few that I have more than one, I have a LOT. I only see the panel when I need to select from a long list of Logins or I want to edit or view something. Hopefully we will find a happy medium in time. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

gpc

[quote name='brenty' timestamp='1312345521' post='36245']

It actually never occurred to me to test sites I use for work, since our customers aren't using most of them. Oddly enough though, I didn't have any trouble saving a new login here -- even a duplicate of my existing one.



In regards to the window size: It isn't set in stone; we will have to tweak it over time and figure out what is the best fit. We still have features to add at this point, so it makes sense to wait a bit. I rarely even see the panel, though. For the vast majority of sites, I have a single Login item and ⌘\ gets me in. For the few that I have more than one, I have a LOT. I only see the panel when I need to select from a long list of Logins or I want to edit or view something. Hopefully we will find a happy medium in time. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

[/quote]



Many of my sites have only one login as well, but I expect to see the panel most of the time because the 1P extension usually needs to be unlocked. (At least that's that's what I expect in my normal usage; at present I spend way too much time trying out lots of logins in close succession in all this beta testing.)



Does ⌘\ work? I tried it just now on a few sites where I have one login and nothing happens. Version 3.7.1 (build 31089), ext 3.7.b9. Snow Leopard.

[Deleted User]

[quote name='gpc' timestamp='1312402211' post='36492']

Many of my sites have only one login as well, but I expect to see the panel most of the time because the 1P extension usually needs to be unlocked. (At least that's that's what I expect in my normal usage; at present I spend way too much time trying out lots of logins in close succession in all this beta testing.)



Does ⌘\ work? I tried it just now on a few sites where I have one login and nothing happens. Version 3.7.1 (build 31089), ext 3.7.b9. Snow Leopard.

[/quote]



It should work without any issues, in b9 it would require the extension to be unlocked first, but I just received word from Dave that he's just pushed 3.7 b10 of the extension that will fix this, so once you unlock the Command + \ shortcut should work.



One thing to try, if it doesn't, is to go to Help > Troubleshooting > Restart Agent from within 1Password itself to see if this helps.



Let me know how that goes,

gpc

[quote name='gpc' timestamp='1312402211' post='36492']

Many of my sites have only one login as well, but I expect to see the panel most of the time because the 1P extension usually needs to be unlocked. (At least that's that's what I expect in my normal usage; at present I spend way too much time trying out lots of logins in close succession in all this beta testing.)



Does ⌘\ work? I tried it just now on a few sites where I have one login and nothing happens. Version 3.7.1 (build 31089), ext 3.7.b9. Snow Leopard.

[/quote]



OK... ⌘\ is working with 3.7.b10. And of course I again saw the panel, because the extension needed unlocking again. I know, I could set a longer autolock period. The point is many users get to see the panel with almost every use of 1P: people who prefer the security of a shorter autolock, people often logging into a site with multiple entries saved in 1P, etc.





I'm not harping on about this to make you change something specific in response, but to make the general point that there's more than one pattern of use, so it's not enough to say "I hardly ever see unpleasant feature X of our program because I use feature Y whenever I can."

khad

Absolutely understood and agreed. We are still working to make it better. Did you see the first version of the Safari 5.1 extension? We have already come a long way in a very short amount of time since Lion was released two weeks ago, and you ain't seen the last of the fixes.



Thanks for all your feedback. Please keep it coming. Every little bit helps us get a better idea of what our customers are looking for.



I'm going to close this thread now since the initial issue has been resolved. If you have anything else to share or questions to ask, please don't hesitate to create a new topic!



Cheers,