User Interfaceīrave has a user-friendly interface that is easy to navigate, with a minimalist design that prioritizes functionality over aesthetics. The app also utilizes a feature called “Brave Shields,” which optimizes page load times by blocking scripts, ads, and trackers that slow down web pages.

Speed and Performanceīrave’s built-in ad-blocker also contributes to its speed and performance, as it reduces the number of resources used by web pages. The app also has a built-in ad-blocker and script blocker, which prevents malicious scripts from running on web pages. Privacy and Securityīrave offers users advanced privacy and security features, such as blocking trackers and intrusive ads, HTTPS Everywhere, and fingerprinting protection.

The app is designed to provide users with a fast, secure, and private browsing experience on their mobile devices. I only use autotype for a handful of websites that I log into so far only seems to be the anomaly.Brave is a web browser application that falls under the category of communication applications. So autotype does work using Brave's existing settings. If instead, I try to use autotype to log into Google using the Brave browser, everything works as expected. So my first thought was maybe autotype is broken under Brave or perhaps one of my Brave settings is interfering. I don't seem to have any problems on Firefox. So KPXC -does- match the entry in the database but apparently only if not using autotype? not using autotype) then it supplies the correct uid.

If, instead, I right-click the username field on the page and tell KPXC to supply the uid/password (eg. So it's as if KPXC fails to match the URL. When I try to use autotype to log into using Brave, KPXC shows a list of all sites in the KP database and asks me to select which credentials to use.

Both browsers are using KeePassXC-browser extension version 1.8.6.1. I'm running KeePassXC v2.7.5 on a Linux machine.

Free brave 1.52.126