Copy not as "agile" in v4 [added Click-Through support in 4.2.BETA-2]

LWinston

Please put this on your list, though it looks like you might have a long one. Copy in v3 worked so much more efficiently. I could move my cursor from browser to 1Pswd and could copy a user name or password with 1 click by clicking anywhere on the field. Now I have to bring focus to 1 pswd by clicking on it, then more carefully click the 'copy" area of the field to copy. It is annoying and less efficient than what you had before. Someone went to a lot of trouble making a nice feature a pain. Put up v3 and v4 side by side (I did) and this is easy to see/experience. Yes, I understand that putting the text "Copy" will help users discover the functionality, but did it have to be at the cost of efficiency?

sjk

Hi, @LWinston.

I'm sorry using Copy with 1P4 has been less efficient for you than with 1P3.

From your description it sounds like you're copying username/password fields from the 1P4 main app, then pasting them into web browser fields. Would it be more direct and efficient to use 1P mini and/or browser extension for accessing that 1Password data? For related information/examples, see posts #2 and #4: here.

I'll note your suggestion with others we're considering for improving access to 1P data from item details in the main app. Thanks!

LWinston

No sjk, I use 1pswd primarily for about 10 banking and finance sites that I log in to frequently - some every day. Each has a multi page log in (user name and password split over multiple screens, security image, additional information for log in such as pet name, first car...) and/or some will not accept input from a program like 1pswd. Bank of America for example. So password mini would not be more efficient because it doesn't work. Now, with v4 I have to double the clicking I do to use your app. Again, v3 would allow me to copy with a single click. With v4 I must first bring "focus" to the app in the finder by clicking on it, then clicking on the password (or user name) to copy. Again, please put v3 and v4 side by side and you can see the difference.

semblance

@LWinston, @sjk - it sounds like this is (at least partly) the same issue that I raised some time ago in the Beta forum. If so, then according to the response to that thread, it should be in the issue tracker already.

Also I agree with @LWinston — you may want to copy all kinds of different fields from 1P to another app, not just the usernames/passwords handled by the browser extensions.

LWinston

Exactly semblance! Same exact issue. You describe it so much clearer...

sjk

Hi, @LWinston.

Now I understand that you (and @semblance) want Click-Through active on at least the Copy controls in 1P4 item details. Thanks for making that clearer to me "over here", @semblance.

I've never personally liked it on OS X (e.g. for reasons in a "classic" Daring Fireball: The Problems With Click-Through article) but certainly understand how it can increase productivity. There's no reason to start another "Click to focus vs. Focus follows pointer vs. Sloppy focus"-style debate about it to make sure the request's in our tracker. :)

semblance

Thanks @sjk, I didn't know it was called "click-through", nor that people had written epic blog posts analysing its pros and cons from every angle imaginable...

I just found the old behaviour much quicker and smoother when copying field values between 1P and another app, when i have them open side-by-side :-)

sjk

Hi, @semblance.

If you have items you like to regularly/repeatedly copy from then keeping their details open in anchored 1P mini windows can be convenient because they support Click-Through. :)

LWinston

How can they do this? Bank of America does not show in mini windows! Some of my financial sites block auto filling of user names and/or passwords or separate them across multiple screens. The simpler quicker copy paste capability was super easy and very enjoyable. I use the heck out of 1password every single day. This, click-through, is a valuable feature and I hope you return it. I was hoping it would be on 4.1.3, but alas...

sjk

Hi, @LWinston.

My understanding is that when 1P4 mini item details windows are inactive their controls have click-through enabled, while the inactive 1P4 main window doesn't. Text for those main window controls (e.g. copy and open and fill) is displayed when the cursor is hovered over them even with the window inactive, which does makes it appear that click-through is supported for them. I'll make sure that's also noted in our tracker.

Here's one reason 1P mini might be missing Login items you expect to be there:

My Account > Login items are not showing up in 1Password mini - AgileBits

This sample item displays okay for me in 1P mini and fills on the main https://www.bankofamerica.com page:

LWinston

Understood sjk, but back on the original topic, can you please please please please please please make "Click-Through active on at least the Copy controls in 1P4 item details"

sjk

I've passed along your re-request for this to our developers, @LWinston. :)

chadseld

Fixed in 4.2.BETA-2

LWinston

Well thank you, but it was "fixed" in v3. Please don't assume users use your app the way you think they do, hope they do, want them to. The world is a complex place and not everything is predictable. One of my main tasks with 1Password is managing financial and medical sites/logins and these sites have multi step logins with keywords/phrases, image verification and more beyond the automatic capabilities of 1Password. The 'click through" feature makes this so much easier and with it absent, my paid v4 upgrade was a poor user experience. Actually, the sync and other issues didn't help with that experience either. I really think you guys can use some more diligence in QA and testing. Oh, and before someone goes on an on about how complex this is, I work with operating room and surgery systems. We know something about system testing.

Jasper

Thank you for the feedback! 1Password 4 was a complete re-write, so it's not that we simply removed the feature. It's something that we always did want to fix (like dteare said), and we've finally had time to give this some attention.

I hope this fix is helpful for you. :)

And since it's now fixed, I'm gonna close this discussion. If you ever need anything else, feel free to create a new discussion.