Safari 5.1 Extension Feedback

Examinus · July 2011

Wow, I think people need to seriously calm down. There's being passionate and there's being borderline offensive. Before people go on a rampage calling for people to be fired and completely trashing 1Password, they need to read this thread and understand why the extension has been updated like this.

fericit.bostan · July 2011

I just upgraded to the latest version of 1Password and the new Safari extension and all I can say is "what a disappointment!" The previous Safari plugin was clean and simple. When I wanted to log into a site I simply clicked the 1P button, selected search, provided a password in the HUD and typed the name I wanted. The new HUD SUCKS!!! I'm presented with a huge, ugly dialog to input my password. Why? Why does this dialog need to be so F***ing huge? Next I would like to simply search for my site but again I have this huge, ugly dialog that presents me with the current site, if any, otherwise I need to select the search tab just to be able to enter my search. Did someone actually think this was an improvement over the previous clean and simple HUD?

And that's not even mentioning the issues I have with the new version. I want to use 1P Safari plugin and go to a site. So I click 1P and I'm presented with the password dialog / HUD. (Did I mention how much I hate this new interface?) Next, I input my password and hit enter and nothing happens. So I try again, and again, and again. It is completely useless. I have to resort to opening 1Password application to go to my sites and copy the user name and password from there to copy and paste my information from 1Password to my browser. What a pain!!! I can't believe that this version was released into the wild. What happened to proper QA before releasing a product? Was the QA team on vacation?

1Password was previously my favorite application on my Mac. Now I simply cringe when I have to use it. Amazing how quickly it went from hero to zero!

nestor · July 2011

Ugh, what happened? I'm not liking the new 1password extension, actually I guess Lion as a whole is starting to bother me more and more. The old menu style extension was so much faster to use than this new one. Count me in as a disappointed user.

paulingraham · July 2011

Will you be dropping an actual 400lb safe on my desk for the next version? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

I'm trying not to just "hate change." With respect, the new popup seems graphically heavy handed to an extreme that deserves comment. I wasn't thrilled when 1Password first started getting a buttload of "chrome", and this takes it to a new level. It seems garish. A little design dignity, please! For a fine positive example, please see how nicely LaunchBar had remained graphically understated over the years, even as its powers have grown and grown. [i]That[/i] is how a power tool should conduct itself.

And it just adds insult to injury that it can't be moved. There is [b]no situation[/b] when an unmoveable object is welcome onscreen. It's just bad UI manners.

F451 · July 2011

Having used the Chrome 1P extension on Google Chrome Canary for quite some now this evolution of Safari and 1P has proved to be no big deal for me. As always, Agile methodically moves along and if the way Agile handled, and with what they have learned from Chrome, is any indication of where the Safari extension will evolved then I have no worries. Yes, at first I was taken back by new means of using 1P and the new dialog boxes in Chrome, but over time that all faded and now I pay it no attention. Enjoy, Agile will get this where it needs to be.

m00dawg · July 2011

[quote name='F451' timestamp='1311361808' post='33062']

Having used the Chrome 1P extension on Google Chrome Canary for quite some now this evolution of Safari and 1P has proved to be no big deal for me. As always, Agile methodically moves along and if the way Agile handled, and with what they have learned from Chrome, is any indication of where the Safari extension will evolved then I have no worries. Yes, at first I was taken back by new means of using 1P and the new dialog boxes in Chrome, but over time that all faded and now I pay it no attention. Enjoy, Agile will get this where it needs to be.

[/quote]

Except I dislike the Chrome plug-in as well. Not to come off as rude to Agile but it's basically the reason I'm not using Chrome at the moment. Compared to the old interface, it's clunky and slow but doesn't add (in fact removes) functionality. Generally not a fan. The old Safari interface was basically perfect - why mess with a good thing, y'know?

richardc · July 2011

Add another voice to the chorus. I really dislike the new look of the extension and think it's a huge step backwards.

I fully understand that Apple have taken away the APIs that you used to use. So some things are no longer possible and others are not yet implemented using the new APIs. That's unfortunate but totally understandable and out of your control. What I am most worried about is the direction that the look and feel has taken.

[quote name='brenty' timestamp='1311297809' post='32839']

Just to summarize a few things not currently implemented but on our agenda:

[list][*][url="http://help.agilebits.com/1Password3/single_keystroke_login.html"]Single-keystroke login[/url] is a top priority.[*]Right-click [url="http://help.agilebits.com/1Password3/contextual_menu.html"]contextual menus[/url] are high on our list.[*]Automatic unlock is [i]not[/i] currently working, but we are working on [i]it![/i][*]URLs with port numbers result in Logins not being offered for a site currently. This is a known issue.[*][url="http://help.agilebits.com/1Password3/http_auth.html"]HTTP Auth prompts[/url] cannot be accessed via the Safari extension API currently, but we hope Apple will add this capability in the future.[/list]

[/quote]

There's no mention in that list of removing the fat from the UI. Please reassure me that it is on your list and that you are not happy with the UI as it stands. It looks like someone just dropped an iPhone app into a popup window, compete with inappropriately large click targets and iphone-like navigation and tool bars.

[url="http://developer.apple.com/library/safari/#documentation/Tools/Conceptual/SafariExtensionGuide/Introduction/Introduction.html"]Safari extensions are allowed to create native popup menus[/url]. Please consider using that UI rather than the html popover you are currently using. I think it's clear from the feedback you are getting that the html based UI has very few fans.

richardc · July 2011

On the problem of HTTP Auth prompts. I wonder if you could work around that problem by (ab)using username:password@example.com urls. Some very rough ideas:

- "Go and Fill" could pass the username and passowrd in the URL for logins which the user has marked as being for HTTP Auth prompts

- Intercept new URL requests before they happen. If the URL is one that 1Password recognises then present your own auth dialog and change the url being requested to include username:password@

- Intercept 403 status codes before safari gets a change to display the standard auth dialog and present your own.

Note that I've no idea if any of those are actually possible using the extension API.

porieux · July 2011

I don't like the latest version of 1Password at all. This new 'panel' that pops up is absolutely terrible and makes it more annoying to use than it is worth.

I understand you had to make some changes in the background to support Safari 5.1, but this new UI change is a big mistake and pretty much breaks the ease of use of the app.

Whether it was a lot of work or not, you should ditch it and go back to the old UI. Stick to incremental improvements.

I'm using the latest version of Snow Leopard by the way.

Paranoid · July 2011

Same for me. I am still using Snow Leopard 10.6.8 with Safari 5.1.

Safari 5.1 feels a little bit faster than before. But because 1Pwd broke its good functionality on Safari 5.1 I consider to downgrade to a previous version.

I would have never updated to Safari 5.1 if I knew it before!

I wanted to upgrade to Lion but this will never happen if it has so many drawbacks.

Colin Helvensteijn · July 2011

[quote name='Examinus' timestamp='1311357872' post='33045']

Wow, I think people need to seriously calm down. There's being passionate and there's being borderline offensive. Before people go on a rampage calling for people to be fired and completely trashing 1Password, they need to read this thread and understand why the extension has been updated like this.

[/quote]

Agreed. People need to understand, this is beta software. And don't say that AgileBits shouldn't have released it as such, because [i]they had no choice[/i]. Apple released Lion and Safari 5.1, so AgileBits had to push out at least [i]something[/i]. Either that, or no support at all for Safari 5.1 users, which happens to include all Lion users. What would you do?

As for the new look & feel of the thing, well, that's just a matter of taste. AgileBits obviously likes it. But hey, scream loud enough and they might change it back to plain menus. But for crying out loud, keep it somewhat civilized. Personal insults surely will not help matters.

mike7599 · July 2011

Just confirming I'm having many of the same issues with the extension. The auto lock is annoying, and it fails to fill many websites. I am pasting and clipping more than half the time. Just installed 3.7.5b2, still having those issues. I've reinstalled the extension with no improvement.

learning curve · July 2011

I haven't goten through the entire forum, so forgive me if this has been asked already.

Can i go back to Safari 5 and the old 1Password? If so, how?

I'm still running Snow Leopard and considering what's happening here, I may NEVER upgrade.

kate21 · July 2011

Oh Lordy, this is not good.

I so agree with Pelted and IanA comments about the new update.

While I am a huge fan of and cheerleader for 1Password, I hate this update.

The pop-up windows irritate me beyond measure. And why the iOS format?? Some of my logins are available and some are not.

Easy and elegant this is not. Paper and pencil are almost looking good to me now.

I haven't even upgraded yet to Lion and now I'm not going to if I'm having this much trouble with 1Password and Snow Leopard.

gmill · July 2011

[quote name='1passwordh4x0r' timestamp='1311309478' post='32846']

Brenty,

I hear you, but I have developed 2 Safari plugins that still work in 5.1.- AutoPB (Auto Private Browser) and URLShortener (A quick and dirty URl shortener - name says it all eh?)... and they are fairly complex.

2 areas I will call out on. First, most plugins work, especially the swizzle stuff which you guys clearly do in your normal plugin. Granted there were changes in 5.1, but that leads me to my second point. Did you not have the developer preview for Lion and 5.1? classdump still shows the API calls in all their glory like all of us plugin developers deal with. Would that not have showed you that you should stick to your guns on the plugin and make the necessary swizzle changes to make your plugin work?

I'm sorry but claiming changes at the last minute is BS. You guys know better than that. Even I had the betas and alphas of this stuff and knew the changes and I'm not even selling my wares...I'm just an open source developer.

My apologies to all readers here... I'm not attacking so please do not take it that way... I'm pointing out the facts and I am happy to discuss this at great length in this forum with their developers at a technical level.

1passwordh4x0r

[/quote]

I would like to hear a response to this from Agile. This guy even offered to work on making the old plugin work for free. WHAT REALLY HAPPENED TO 1PASSWORD?

Any who is responsible for the ugly user interface? Just to add a positive note here. I loved the old 1Password and put all my friends family and clients on it. The new 1PASSWORD is in your face bad!

[Deleted User] · July 2011

Hello everyone!

I just wanted to jump in and let everyone know that we are listening to all of your comments.

We appreciate those who've provided positive thoughts, and/or have advised patience while AgileBits works our way through the relatively new Safari 5.1 code changes & restrictions.

However, we also appreciate the less & much than less positive comments that have been posted. We need to know what our customers want in 1Password's functionality, and we do care if a current version does not provide the user experience people want/demand.

To everyone who's reading this thread, please know that we are working diligently to upgrade the Safari 5.1 extension for all those feature requests that we can. However, there have been many changes to the way Safari allows third-party applications to integrate, and the change has required AgileBits to rewrite the previous code used to create the functionality that previous 1Password users have grown accustomed to.

One post in this thread that I believe captures the optimism that we at AgileBits feel for the near term and long term future of the Safari 5.1 extension comes from F451:

[quote name='F451' timestamp='1311361808' post='33062']

Having used the Chrome 1P extension on Google Chrome Canary for quite some now this evolution of Safari and 1P has proved to be no big deal for me. As always, Agile methodically moves along and if the way Agile handled, and with what they have learned from Chrome, is any indication of where the Safari extension will evolved then I have no worries. Yes, at first I was taken back by new means of using 1P and the new dialog boxes in Chrome, but over time that all faded and now I pay it no attention. Enjoy, Agile will get this where it needs to be.

[/quote]

We understand the frustration voiced by several of the members who've posted in this thread or elsewhere, but please know that we are not sitting still during these early stages of Lion's official release.

We will continue to request everyone's feedback, both positive and negative. However, I request that those who post, do so in a respectful manner.

Thanks for your passion. We look forward to proving F451 correct.

Cheers!

Brandt

roustem · July 2011

[quote name='1passwordh4x0r' timestamp='1311309478' post='32846']

Brenty,

I hear you, but I have developed 2 Safari plugins that still work in 5.1.- AutoPB (Auto Private Browser) and URLShortener (A quick and dirty URl shortener - name says it all eh?)... and they are fairly complex.

2 areas I will call out on. First, most plugins work, especially the swizzle stuff which you guys clearly do in your normal plugin. Granted there were changes in 5.1, but that leads me to my second point. Did you not have the developer preview for Lion and 5.1? classdump still shows the API calls in all their glory like all of us plugin developers deal with. Would that not have showed you that you should stick to your guns on the plugin and make the necessary swizzle changes to make your plugin work?

I'm sorry but claiming changes at the last minute is BS. You guys know better than that. Even I had the betas and alphas of this stuff and knew the changes and I'm not even selling my wares...I'm just an open source developer.

My apologies to all readers here... I'm not attacking so please do not take it that way... I'm pointing out the facts and I am happy to discuss this at great length in this forum with their developers at a technical level.

1passwordh4x0r

[/quote]

Thanks for adding your perspective, 1passwordh4x0r!

I understand where you are coming from. The old swizzling ways were in many cases much easier than using the official API <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

We spent quite a bit of time working on the old code in Lion, right until the Scripting Additions were killed just before the GM release.

Some of the class dump output that you see is misleading. Safari includes both WebKit and WebKit2 code at the moment. However, it is certainly running the WebKit2 engine by default. The WebKit2 engine written in C++ and it also runs in isolated process (see "Safari Web Content" process). I even played with the idea of swizzing the C++ pointers for some time but in the end it is just too fragile.

I wish Apple would have killed the Scripting Additions earlier then we'd have spent 100% of our time developing for Lion with the the official APIs.

I understand the frustration and we are not happy with the way the things are at the moment. Please keep the constructive feedback coming and we will keep pushing the updates.

brenty · July 2011

[quote name='richardc' timestamp='1311362791' post='33068']

On the problem of HTTP Auth prompts. I wonder if you could work around that problem by (ab)using username:password@example.com urls. Some very rough ideas:

- "Go and Fill" could pass the username and passowrd in the URL for logins which the user has marked as being for HTTP Auth prompts

- Intercept new URL requests before they happen. If the URL is one that 1Password recognises then present your own auth dialog and change the url being requested to include username:password@

- Intercept 403 status codes before safari gets a change to display the standard auth dialog and present your own.

Note that I've no idea if any of those are actually possible using the extension API.

[/quote]

That is actually a neat idea, richardc. The only problem -- and this is a big one here -- is that URLs are sent in the clear. Security is very important to us, and we just can't be sending usernames and passwords unencrypted in packets, as they could easily be collected or intentionally intercepted, either on a local network on at any point en route to the destination.

This is an example of why developing a new extension from scratch isn't as simple as it appears to be. The things that are seen are just the tip of the iceberg, and a lot of thought and hard work (and testing!) went into making sure that when you are using 1Password in your browser, it is done securely.

WhiningMonkey · July 2011

Just registered to say that I HATE having to enter my password when I am trying to use the browser extension.

I am at home, not on a laptop and I want the browser extension to make things faster for me, not slow me down.

I have "Never prompt me for master password" selected but the stupid Safari extension doesn't seem to know that....

Grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr....

Otherwise let me just say that I love 1Password overall and it has made my life personally and professionally much easier since I have been using it!

Keep coding!

khad · July 2011

Welcome to the forums, WhiningMonkey!

Lack of automatic unlock in Safari 5.1 is [url="http://help.agilebits.com/1Password3/automatic_unlock.html"]a known issue that we are working on[/url]. Thanks for asking about it.

[quote]Otherwise let me just say that I love 1Password overall and it has made my life personally and professionally much easier since I have been using it![/quote]

Cheers! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

IanA · July 2011

For me it's the interaction speed that I miss most about the old version.

Clicking the 1P button and having it animate in and then bounce seems unnecessary, and the interaction of buttons within the extension (once open) is also quite slow.

Moving from "Logins for this site" and "All Logins" has a split second delay and that delay makes me think that it's not working.

In terms of clarity I also find it hard to read the button titles and icons in their current embossed state (see image).

[img]https://img.skitch.com/20110723-esi2bq64rmjby2wjwidikfknde.jpg[/img]

Removing one level of drill downs could be accomplished by having Identities and Credit Cards already available, similar to Logins. Mockup attached.

[img]https://img.skitch.com/20110723-x272um5q73sne56waawisg1cj3.jpg[/img]

leicaman · July 2011

The previous way to hit command \ was elegant and fast. This thing right now is refusing to work. But it's just the horrendous bulk of the interface is driving me batty. This is really a bad choice and I am a big, big fan of 1Password. (Lion and Safari 5.1) and this is just terrible. Do. Not. Like.

But what's most annoying is that this evening it simply stopped working. I hit Command \ and the pop over comes up, and I type my password in (I understand about having to type it so often while you work things out) and hit Enter (Return) and nothing happens. Zip. Nada.

But now that I got the update, it's working again. I really don't like this interface. I think it's time to go back to the drawing board. Smaller is better! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/rolleyes.gif' class='bbc_emoticon' alt=':rolleyes:' />

MikeT · July 2011

Hi guys,

The latest extension update, 1Password 3.6.5.Beta-26, now includes the ability to log in without seeing the extension window if you only have one login on the site. It should be automatically updated for everybody by now if Safari has the auto-update enabled for the extensions.

[quote name='IanA' timestamp='1311397251' post='33197'][color="#1C2837"][size="2"]For me it's the interaction speed that I miss most about the old version.[/size][/color] [color="#1C2837"][size="2"]Clicking the 1P button and having it animate in and then bounce seems unnecessary, and the interaction of buttons within the extension (once open) is also quite slow.[/quote][/size][/color]

[size="2"][color="#1c2837"]I do understand your concerns about this. The animations weren’t added just for the sake of it, it’s to showcase that 1Password is working on encrypting and decrypting your data. The new extension does a lot more heavy work than the previous extension. Without the animations, it’d look like the extension is frozen for a few microseconds. We’re continuing to work on the performance optimizations.[/color][/size]

[size="2"][color="#1c2837"]As for the text clarity, I can see why it would be hard to read. We’ll look into that. Thank you for bringing that up. [/color][/size]

desven · July 2011

Hi,

I like the new interface. Using Tab and search is a real good way for finding logins in the extension menu. The is only one big problem with this.

Example:

1. Go to http://www.anysite.com/login and hit CMD+/

2. Empty menu comes up and you hit Tab and search for "anysite"

3. You find an entry for http://www.anysite.com/shop with the correct login credentials

4. You select it an hit return

5. Safari does not fill out http://www.anysite.com/login but goes to http://www.anysite.com/shop

Shouldn't it just fill out the fields?

Greetings

Sven

craigminah · July 2011

I really dislike a few things about 1Password for Safari 5.1.

1. For most of my web sites I only have one password in 1Password (ironic, eh) so why does 1Password pop up a window asking which password I want to use though it presents me (so it knows) I only have the one password to select in the first place? One of the things that made 1Password so popular IMO was that I just press command-\ and it auto fills unobtrively (e.g. no pop selection window unless I had multiple choices).

2. The 1Password popup window looks out of place and the animation is annoying.

Alexis1537 · July 2011

[quote name='khad' timestamp='1311192168' post='32457']

Those of you who gave them, thank you for the compliments! We really appreciate them, and we thank you for taking the time to post about the new Safari 5.1 extension.

As well as being [url="http://help.agilebits.com/1Password3/contextual_menu.html"]mentioned in the User Guide[/url] as a [url="http://help.agilebits.com/1Password3/troubleshooting_safari_5.1.html#other_known_issues"]known issue[/url], I have also addressed the contextual menu above a couple times. Thanks for letting us know you would like to see this as well!

This is likewise on our radar. Thanks for the reminder!

Please read above. [url="http://help.agilebits.com/1Password3/single_keystroke_login.html"]Single-keystroke login[/url] is on the way, and you don't have to use a pointing device unless you prefer that. The new Safari 5.1 extension supports a [url="http://help.agilebits.com/1Password3/keyboard_shortcuts.html"]full range of keyboard shortcuts[/url], so it can be operated completely via the keyboard. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

As has been mentioned previously, we are now using the native Safari extension APIs which allow us to provide a much richer experience in the extension than ever before. This also means that as we update the extension, you will automatically get the new versions without having to update the main 1Password application. That's right. You won't have to do anything to get the Safari extension updates as we roll them out. (And there are [b]many[/b] on the way!) <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />

Keep the feedback coming!

[/quote]

Can I also add (if it hasn't already been covered elsewhere) that the data in forms no longer fill or submit when I select the login in the new login window. This is also a major step backwards and looks like a major bug. Tis applies whether or not I use Chrome or Safari.

Thanks,

Alex

richardc · July 2011

[quote name='brenty' timestamp='1311385961' post='33152']

That is actually a neat idea, richardc. The only problem -- and this is a big one here -- is that URLs are sent in the clear. Security is very important to us, and we just can't be sending usernames and passwords unencrypted in packets, as they could easily be collected or intentionally intercepted, either on a local network on at any point en route to the destination.

[/quote]

For [url="http://en.wikipedia.org/wiki/Basic_access_authentication"]basic auth[/url] I don't think that's a problem. If you're using http then the credentials are in the clear either way. If you are using https then they are not. So putting the credentials in the URL rather than the "Authorization" header doesn't make any difference to a packet snooper.

I hadn't consider [url="http://en.wikipedia.org/wiki/Digest_Access_Authentication"]digest auth[/url] in my original message. For that method, you are right that sending the credentials in the URL would be bad and wrong. Not only would it be insecure, I'm not even sure if it would work. To support digest auth your extension would need to be able to edit http request headers. I've no idea if that's allowed. I suspect not.

[Deleted User] · July 2011

[quote name='Alexis1537' timestamp='1311421238' post='33281']

Can I also add (if it hasn't already been covered elsewhere) that the data in forms no longer fill or submit when I select the login in the new login window. This is also a major step backwards and looks like a major bug. Tis applies whether or not I use Chrome or Safari.

Thanks,

Alex

[/quote]

Hello Alex and welcome to the Forums!

There were two BETA updates released yesterday (July 22nd), that addressed several issues. You can review the release notes here: [url="http://agilebits.com/products/1Password/versions/betas/#v31072"]http://agilebits.com/products/1Password/versions/betas/#v31072[/url]

After updating, I am now able to fill and submit from the Safari extension by clicking on the extension entry. I'm also able to double-click an entry in the 1Password 3 for Mac desktop application, and Safari now performs the Go & Fill function as it did in the past.

If you haven't updated to our latest version, 3.6.5.BETA-3, and you do not mind trying out BETA software, you can do so my going into 1Password > Preferences... and ensuring the "Include Beta versions" checkbox is checked on the Updates tab. Next, select 1Password > Check for Updates... You should see a popup box offering the latest version of 1Password, be it stable or BETA. Download, install and relaunch 1P.

In order to ensure that you are using the latest Safari 5.1 browser extension, in Safari 5.1 go to Safari > Preferences... > Extensions. Click on 1Password ß and see what version is listed. As of this writing, the current extension is 3.6.5.BETA-27.

Please let us know if the latest updates have corrected the issues you reported.

Cheers!

Brandt

[Deleted User] · July 2011

[quote name='craigminah' timestamp='1311419318' post='33280']

I really dislike a few things about 1Password for Safari 5.1.

1. For most of my web sites I only have one password in 1Password (ironic, eh) so why does 1Password pop up a window asking which password I want to use though it presents me (so it knows) I only have the one password to select in the first place? One of the things that made 1Password so popular IMO was that I just press command-\ and it auto fills unobtrively (e.g. no pop selection window unless I had multiple choices).

2. The 1Password popup window looks out of place and the animation is annoying.

[/quote]

Hello craigminah and welcome to the Forums!

Thanks for your feedback. We are working very hard to correct each odd behavior as quickly as we can.

Regarding #1

Please refer to my previous post regarding recent updates we released. Please update your 1Password application and Safari extension, and let us know if you are still experiencing the same behavior,. If so, please provide details regarding regarding the versions you are running and the URLs where you experience this problem

Regarding #2

We are working on tweaks to the Safari UI. I do not have any new information to report at this time, but please check back for any updates.

Cheers!

Brandt

[Deleted User] · July 2011

[quote name='desven' timestamp='1311417292' post='33278']

Hi,

I like the new interface. Using Tab and search is a real good way for finding logins in the extension menu. The is only one big problem with this.

Example:

1. Go to [url="http://www.anysite.com/login"]http://www.anysite.com/login[/url] and hit CMD+/

2. Empty menu comes up and you hit Tab and search for "anysite"

3. You find an entry for [url="http://www.anysite.com/shop"]http://www.anysite.com/shop[/url] with the correct login credentials

4. You select it an hit return

5. Safari does not fill out [url="http://www.anysite.com/login"]http://www.anysite.com/login[/url] but goes to [url="http://www.anysite.com/shop"]http://www.anysite.com/shop[/url]

Shouldn't it just fill out the fields?

Greetings

Sven

[/quote]

Hello Sven and welcome to the Forums!

The autosubmit problem is a known issue with Safari 5.1, but we are working hard on a solution.

Please refer to Khad's post in a similar thread for additional information: [url="http://forum.agile.ws/index.php?/topic/5763-1password-lion/page__view__findpost__p__33248"]Autosubmit Preferences[/url]

I'm sorry that I do not have a better answer for you at this time.

Cheers!

Brandt

Safari 5.1 Extension Feedback

Comments