![]() ![]() ![]() I'd like to share some decisions and progress: Would this extension solve your day-to-day needs or something is missing? What do you think? Is there demand for such extension? any other UI "injected" into websites: just don't do it! it looks and behaves not as it shouldįor example, we can start with something like this: icons, buttons, different forms of auto-completion, etc.saving fields back to KeeWeb: again the absence of standards and APIs makes it complicated.auto-fill without user interaction: this is a product in itself that requires dedication and careful development due to vulnerabilities it can introduce and flexibility of HTML forms.configurable shortcuts for common actions.trigger the auto-type selection pop-up if a matching entry can't be found automatically.insert username / password / both / auto / otp / other field.The extension can provide the bare minimum that can be expected from it: Own extension doesn't seem to be hard to implement, assuming that we can avoid overloading it with features. It will give us a possibility to connect to KeePassXC-browser, as well as build our own extension based on it. The protocol used in KeePassXC-browser called keepassxc-protocol can be used by different extensions, so we should support it in KeeWeb. It doesn't work with Safari and the maintainers don't seem to be enthusiastic about it.There's an ethical dilemma regarding overwriting the application it opens, I would prefer describing it in the app but leave the choice to the user, so that this option is not offered by default but there's a possibility to do so with a bit of configuration.There's a lot of critique about its security and I see that the browser extensions are not actively developed. KeePassHttp or KeeWebHttp seems to be going nowhere, supporting it doesn't make sense anymore. Since people here may find it interesting, I'll share my thoughts about supporting browser extensions in KeeWeb. ![]()
0 Comments
Leave a Reply. |