Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Max_ag
1Password Team
2 years agoExperiment #4 – New interface in 1Password.com’s vault view
Hi Folks!
Today we’re bringing you a beta version of a major update to the vault item view interface on 1Password.com. Our goal is to align the design with the main desktop application as well as ...
1P_Rob
1Password Team
1 year agoAfter turning off all of the extensions,1Password allowed me to see the item details. What is strange is that I had added the 1Password extension AFTER I had this problem so maybe another extension?
Dfox I'm glad you got it working. Were you able to figure out which extension caused the problem by turning them back on one by one? You may have to reload the page after each one to get an accurate test.
See attached screenshot where we have a guest user and have only share one vault with them titled "Shared" and they are able to use that in the old ui and view all the items in the "shared" vault, However, after switching to new UI, there is nothing that appears for the same user, see attached image where there is no vault visible.
balajisampathnc thank you for including screenshots! That clued me in to the problem here. In the first screenshot you can see that the user has Travel Mode enabled. That means that any vaults that are not marked "safe for travel" will be hidden from our apps. The old version of the web app did not respect that setting, but the new version does. If you turn off travel mode for that user, you should be able to see the Shared vault again. Let me know if that doesn't work.
In the old version, clicking on the document from the list would load it in the main window and display the image as a preview. In the new version, it just shows the icon of the image, the filename, and a link to download - no preview.
PersisNuva thank you for outlining your use case for us. That's a wild scheme, and I'm genuinely sorry for the headache this change has caused there. As you noted, this is how 1Password works in all the other apps, so it will take a bit of effort to support this again, but I'm passing your feedback on to our team, and we'll see what we can do.
Most often, my method of launching the 1Password web app is by either creating or editing an item from the browser extension.
d9a that's helpful, thank you! In that case, you end up basically having to load both web apps before anything shows up, so I definitely see how that adds up to be annoying.
Looking more closely at the "switching back and forth" approach, another difference is that the old UI automatically loads the first item in the list, and the new one doesn't load anything, saving it a bunch of extra work. I'm curious if you see the same slowdowns as I am if you ask it to load a more complex view right off the bat.
d9a Loading a single item usually won't add more than a split second unless it has an unusually large amount of data in it. The majority of the loading time is getting the web app code from the server, signing in, and getting all the vaults and list of items.
Regardless I did some more testing, this time from the browser extension. From a cold start, clicking edit in the extension, it took about 10 seconds for the item to show up for me in the new view in edit mode. Subsequent tests were much faster though, about 3.5 seconds each time. Meanwhile the old view was right at 2 seconds as before.
Any time we update the web app, there's new code to be downloaded, and unfortunately a good chunk of it is hard to split into pieces that can be cached. So I think that's what happened with my 10 second load. I hadn't loaded that view yet today in production (and we just put out a new version today), so I had to download it. Then subsequent attempts used the cached version.
when you've already established a baseline of what's possible with the old version, your cold-boot times shouldn't be getting worse.
I agree with you. We have some work to do on this.
We've just begun an effort that will make startup much snappier for regular users like you by maintaining an offline (encrypted) cache of data like our other apps do. This is something the old version has never done. Once you have the code cached and the data cached, the only barrier will be that initial sign-in. I'd like to see us break that sign-in screen out so we're not loading two whole apps every time. That's its own project and team.
I've got a ton of screen space and I'd like less of the pixels to be white.
Have you heard of dark mode? 🤪
I do get where you're coming from. My hope is with a unified experience across desktop and web we can begin focusing on improving the experience for everyone, while realizing that no decision will make everyone happy.
more like someone's moved all my furniture around by a few inches so I keep stubbing my toe on things I didn't expect to be there
Yeah. I feel that for you too. If only we had unified things from the beginning. 🥲
Ctrl+R is a fairly universal shortcut in every browser I'm aware of for reloading the page.
Yeah, we may need to find a better one. We're aware of this of course, but it works in Chrome and Firefox, and Shift-Ctrl-R can still be used to reload the page.
I can't believe I have to say this, but shipping a half-baked redesign is not a good thing.
Well, we're going to disagree about what constitutes half-baked, and code at 1Password is always under active development. But I hear you.
We have rather large SECURE NOTES, and since we switched to the new interface, a new issue is occurring semi-regularly: when we go to edit a secure note in Chrome on Mac, we get a spinner for a very very long time before we can actually type in the secure note area.
jn1480 when you're editing a secure note, are you clicking "Edit" inside the web app itself or from inside the browser extension? The former only takes about half a second for me, but the latter is the performance problem discussed above.
Also new this morning when we go to click the SAVE button nothing happens.
jn1480 what browser and operating system are you using? I'm not able to reproduce this problem.
Adding a note about the latency - both on the mobile app as well as in the browser extension, everything feels more 'sluggish'... it's painfully slow compared to the old UI.
rrrobot I can't tell if we're talking about the same thing. This forum thread is about the web app at my.1password.com. The browser extension and mobile apps are not affected by this change. If you're experiencing trouble with those, I don't have the expertise to assist you.
one of the features keeping me a 1password subscriber is the full item history capability which you are essentially removing by copying desktop app
Hey, PhrozenAsh, as MerryBit said, item history is now under "Last edited". It actually works much better than it did before. You can preview each version before deciding which one to restore.
However, as one who has to find the setting to increase the time-out from 10 to 300 minutes at least once a day, I am disappointed you haven't made this annoying change more easily activated.
Steve7FJ I just recently learned there's a bug with this setting that can cause it to be reset in several cases. We're working on a fix. Sorry about that! We should also bring this into the new app's settings, you're right.
cc: Icannotturnoffqa
if I am viewing a record in a browser and duplicate the tab, 1Password makes me log in again in the new tab.
Icannotturnoffqa this is what I was attempting to answer in my last post:
1Password is not like other web apps in many ways, but a really big one is that we don't rely simply on an authentication token to sign you in. Typically an authentication token like that is stored in a cookie in your browser, and if anyone had access to your device, they could access the token value and also the account it gives you access to.
With 1Password, though, we need more than an authentication token. We need you to have encryption keys to decrypt your data in the browser. If we were to just save those in a cookie in your browser, someone could steal them and all of your data just by having brief access to your device. So we're needing to get a bit more creative in how we allow a session to be persisted to minimize the risk to you.
When you open a new tab, it's like reinstalling the app. We don't have access to your encryption keys in that tab. I'm working on a proposal that will allow new tabs to communicate with existing tabs to ask for those keys, but it's necessarily more complicated than a typical web app.
It's impossible to upload an image for the login item in the new design.
vad1mator yes, adding custom icons for items isn't supported right now. Today's release included support for viewing existing custom icons. Editing them will come in a future version. You can still edit custom icons using the desktop and mobile apps.
Delay can be 4-5secs on selecting an entry.
AlfredMNZ are you selecting the entry from inside the web app or are you using the Edit button in the browser extension?
Why does 1Password always open in "employee" view?
AlfredMNZ if you are using the browser extension like I'm supposing, when you edit an item you'll be taken directly to the vault that item is in. Is that what you mean?
I still have the issue where 1Password on first opening shows entries without tags. I have to select "edit and cancel" to go to full screen to see tags. I search by tags.
I'm sorry, AlfredMNZ, I can't reproduce this issue. Can you outline exactly the steps you're taking? Is this a new issue or was this a problem with the old version too?