michaelk83

1. Looks like too much vertical padding on the tag labels (inside the green rectangles). 2. Could reduce at least the vertical padding of the outer text box (outside the...

You can sort of do this already with the use of a _key database_, via the [Auto-Open feature](https://keepassxc.org/docs/KeePassXC_UserGuide#_automatic_database_opening). Each family member would get their own key database with their own...

> would you agree that a new Issue (Feature Request) could be opened for a flag for AutoType quasi `OpenInForeground = (False | True)` @droidmonkey Is this something you may...

@droidmonkey Just a reminder, @Aetf was waiting on https://github.com/keepassxreboot/keepassxc/pull/8591#issuecomment-1330287836 to land before working on more Secret Service stuff, which in turn seems to be waiting on #8480.

> if you have any suggestions to improve the editor UI Maybe move the type dropdown to the left end of the buttons row? This way, it won't take up...

> We can’t see the difference between these sorts of text by MIME type, because it’s just text/plain. There are specific MIME types for Markdown, HTML, etc. text/plain is the...

> I found #9981 but the problem there seems to have been different. Different circumstances, same bug. See also https://bugs.kde.org/show_bug.cgi?id=312325#c39

It's not so much "backwards" compatibility, but _current_ KDE compatibility. KDE (specifically Klipper and KWalletManager) explicitly use `x-kde-passwordManagerHint` (not `text/...`) to mark sensitive data in the clipboard. You're correct that...

`vnd.keepassxc.` is also not necessary. This should ideally be a more general thing, denoting any security-sensitive text, particularly for clipboard use. Even without actual IANA registration, it's still better to...

According to https://www.freedesktop.org/wiki/Specifications > If you would like to propose a new specification, or a change to an existing specification, please file an issue on the spec under the GitLab...