Forum Discussion

kuoirad's avatar
kuoirad
Occasional Contributor
4 years ago

Problems with new 1PW extension (Chrome) and saving new or updating passwords

Been using 1Password for years both privately and at work, on Mac, Windows and Android. Recently got pushed onto the "new" 1PW extension (Chrome) after installing 1PW 8 on a machine at work, decided...
browser extension
kuoirad's avatar
kuoirad
Occasional Contributor
4 years ago

ag_chantelle :

Please do. Not having it prompt to save a new login feels like a MAJOR regression in functionality to me.

However, shouldn't the created password at least be saved itself? Not as a login type, but just a password type? Does that make sense?

With regards to the UI, 1PW 8 feels to me like Android 12 (the OS; also not a fan of the new UI there) does - things are bigger, rounder, glossier/brighter, and "squishier"-seeming. Maybe best described as more "candy-like"? I'm definitely more of a fan of more muted/matte and flat in visual design, but that's just me. I'll keep my other work computers where I've got 1PW installed on the 7.x tree while I can.

I'm guessing with the focus for the browser extension moving to what was called 1Password X and away from the older Classic extension, AgileBits is unifying the UI/UX in the standalone app as well. I can live with it, I'm just not a fan. It's just look and feel and I try really hard to just roll with look and feel issues unless they actually get in my way. I'm more concerned about the autosave issue for this thread and the credit card autofill issue I referenced where I have concerns about the changes in functionality.

Thanks!