Jonathan White

We need to put a special substitution in the css: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization#predefined_messages ``` body { direction: __MSG_@@bidi_dir__; } div#header { margin-bottom: 1.05em; overflow: hidden; padding-bottom: 1.5em; padding-__MSG_@@bidi_start_edge__: 0; padding-__MSG_@@bidi_end_edge__: 1.5em; position:...

We are never going to implement ALL entries being sent to the browser. You must use the actual application for that. This is a security control. What is the value...

This means we would break support for HTTP Basic Auth only on Chromium based browsers until they support that API?

We offer a better solution called Auto-Type. With my most recent major refactor, Auto-Type will allow you to search the database for an entry and type it in very fast....

See https://keepassxc.org/docs/KeePassXC_UserGuide.html#_auto_type on how to use it and https://github.com/keepassxreboot/keepassxc/pull/5864 for the improvements PR scheduled for release with keepassxc 2.7.0

If you don't see the entries already then you haven't configured them to work with the browser extension. Check that the entry url is correct and you haven't blocked it...

Ok sorry, you are correct, sometimes the extension pop-up does not show the available entry list, that is a bug.

Yes, but only if there are login input fields detected on the page.

Probably not, this would trigger a credential request on every page. If you don't have that auto authorized you would see the requesting credentials pop-up from keepassxc every time you...

Not until Safari supports the Web Extensions API. Please see https://stackoverflow.com/questions/47435082/will-safari-ever-support-webextensions-api