My user id does not autofill on https://www.fidelity.com/atwork anymore after recent update.
1Password Version: 1Password 7 Version 7.2.4 (70204000) AgileBits StoExtension Version: 7.2.4OS Version: osx 10.14.2Sync Type: noneReferrer: forum-search:userid does not autofill
@Kaiz212: Can you be more specific? What's happening exactly? I seem to be able to fill it here. What browser and extension versions are you using?
I'm using Safari on a Macbook Pro. The extension version is 7.2.4. On the Mac, neither Chrome nor Firefox fill the userid on this website: https://nb.fidelity.com/public/nb/atwork/home. The userid does fill on Windows 10 PC.
Thank you for the report. I will file a bug report but until we get something in place I'm afraid it looks like you'll have to copy and paste on the Mac. I am sorry about that.
As I don't know Fidelity there is one question you could help me with. Is that URL specific to some service and does it mean the dedicated page at https://login.fidelity.com/ftgw/Fas/Fidelity/RtlCust/Login/Init?AuthRedUrl=https://oltx.fidelity.com/ftgw/fbc/ofsummary/defaultPage reachable from www.fidelity.com doesn't allow you to sign in with those credentials?
I don't have a good understanding of Fidelity's various login portals and probably haven't even seen all of them, but for me it seems that signing into my account just about anywhere on their site allows me to access the account I have. There may be exceptions that I haven't encountered yet though.
Answer to littlebobbytables: The URL, https://www.fidelity.com/atwork is not specific to a service. It's a portal to view and manage retirement plans for employees of a large company. For a number of years that I've been using 1Password, I never had a problem. A few days ago, the problem started in browser extensions in Safari, Chrome and Firefox after 1Password update. Currently, my workaround is to open the app, copy the UserID and paste it in the browser, then use the extension to insert the password.
@Kaiz212: Sorry stick my nose in, but I've been looking into this since I have a Fidelity account myself, which helps to some degree with testing. I think I've narrowed it down to a regression in some of our recent filling engine changes. Regrettably we don't have the same release in all of our apps since they necessarily have different development cycles, but hopefully we'll be able to address this and get it out in updates to each of them before long. Unfortunately sometimes making a change to help with one site can have unforeseen consequences for others, but we'll get this fixed. Thank you for bringing it to our attention!