Cannot copy/paste field titles
When adding fields, 1P8 has eliminated the ability to copy and paste field titles. Please bring that back.
1Password Version: 8.8.x beta
Extension Version: n/a
OS Version: macOS 12.4
Browser:_ n/a
Comments
-
This does indeed appear to be fixed in beta 80800197, as well as the ability to copy the version ID from the "about" window. Thanks.
0 -
Ok, now it seems broken again in version 80800215, and I can no longer copy anything out of a field title.
Note that I can paste, however.
0 -
Any updates? I'm on the latest beta (80900001), and I still cannot copy field titles out of user-added fields (and some other places) via any of application-menu, context-menu or a shortcut.
0 -
In edit mode, on a brand new (or existing) item on the latest beta (80900001), I cannot copy the title of a field in an additional section. Attached is an image showing the copy menu item greyed out. I also cannot copy with Cmd+c.
0 -
Hi @esquared:
Thanks for those additional details. I did some testing with additional sections, and was able to replicate this for the title of password fields. I've filed an internal issue, so hopefully we can get it sorted out in the future.
Jack
ref: dev/core/core#16160
0 -
That begs the question - what's different about "password" field types? Really, that goes back to the premise that something in the (strongly-typed OO?) implementation is leaking into the UI. In the ideal case, there would be no difference between the titles of any field type - or for that matter, the field values either. That's probably the root of the issue of changing the type of a field.
0 -
@Jack.P_1Por @PeterG_1P - this is still an issue I'm facing regularly, and yet another reason I continue to run 1Password7 side-by-side with 1Password8. Can you please ensure that this bug is addressed permanently? It seems that it works for a while and then reverts. On the latest beta (1Password for Mac 8.10.0 (81000020)), I can no longer cut/copy field titles, though I can paste.
0 -
Hi @esquared, thanks for letting us know what you've experienced here (and apologies for the delayed reply as well).
We're tracking this issue and I'll make sure our developers have your report. And while I can't offer a specific timeline on this one, it does look like a bug so we'll certainly work to get it fixed permanently. Thanks again for raising it!
0