_Disclaimer: I am using chromeIPass **and** KeePassXC-Browser at the same time, for different databases. It's either this affecting, or the fact that KeePassXC DB that's locked._ I have a website, requesting BasicAuth. For that website KeePass-DB has the data, not KeePassXC-DB. KeePassXC-DB is locked, KeePass-DB is unlocked. Navigating to the webpage does not provide me (or chromeIPass) a prompt to fill the data that are requested, and page loads forever ## Expected Behavior * KeePassXC either prompts me to unlock the DB. If I choose to unlock, then: * If credentials are found, KeePassXC-Browser fills and submits. * If credentials are not found, or I opted not to unlock the DB, then: * Give the next "hook" a chance, or\ * At least return me the prompt ## Current Behavior Page is _gray-loading_ forever ## Possible Solution _See expected_ ## Steps to Reproduce (for bugs) _See first 3 paragraphs_ ## Debug info KeePassXC - 2.3.4 (I have updated 2.4.1, but haven't restarted the browser during that time. Could it be that it's cached on start?) KeePassXC-Browser - 1.3.3 Operating system: Linux x86_64 / Ubuntu 16.04.5 Browser: Chrome/Chromium 73.0.3683.103

Extension hogs BasicAuth, even if it has no credentials to provide (if used in conjuction with chromeIPass) #473

Company

Community

Support

Connect