![]() ![]() These variations appear to me to be mostly attributable to differences in website coding, not to browsers and password managers. Some password managers can manually populate log-in fields while others require that I cut-and-paste user names and passwords. And how specific password managers and specific websites interact varies. Some other websites automatically populate these fields when I initally navigate to the website. Any ideas what it can be If this is not getting better I would need to drop Brave for another browser. I’ve found this to be the case for different password managers and different browsers including at least one browser that’s not Chromium-based.įor example, logging into this website - the one that presumably you’re looking at right now - initially presents me with blank user and password fields. I’ve not been shy with some of my criticisms of Brave, but this may be beyond Brave’s (or any browser’s) control. My experience with password managers and browsers: how a specific website handles logging in depends mostly on the website’s coding, not on either the browser or password manager. I have added the 1 Password extension to the Brave Browser What I would like to happen is to have Brave authenticate me to 1 Password when I fire up the browser and then use the 1 Password store to automatically log me on when I go to a site. How it works today is that I go to a site, click on logon, click on 1 Password, authenticate to 1 Password, click on the site in 1 Password and it logs me in. I would like Brave to read 1 Password and auto fill my ID and password. I really don’t want my passwords saved in Brave / or however it’s done when you click on “Save logon”. What I would like to do is to have 1 Password auto fill my ID & Password when I go to a site. Hopefully this issue has been resolved, I just can’t find it and as usual doing something wrong. I’m an old man and am not real good at searching for answers on these types of forums.
0 Comments
Leave a Reply. |