Issues with DuckDuckGo Browser for Desktop Integration

For a few months now, the DuckDuckGo Browser for Desktop offers native BitWarden integration that works with the BitWarden Desktop app. At first sight, it looks fantastic. However, upon really trying it out, sadly there are many flaws – some of which must be bugs.
I’m aware it’s a fairly new feature, and issues may not even be BW’s responsibility, but rather be due to delays on DDG’s end – after all the DDG Browser is still in “beta” – so obviously we shouldn’t expect a perfect product. But, since I haven’t found any place where these things are being discussed here’s a (non-exhaustive) list … anyone who is super excited about the DDG-BW collaboration but also frustrated at things not working … you’re not alone and please add your own observations.
Also suggestions would be nice where best to raise these issues with people who are more deeply involved with these projects – would it make sense to create a ticket/tickets on GitHub? … BW or DDG?

So here are the main issues from what I could observe:

The BitWarden browser extensions for other browsers have a dedicated settings tab where one can select, for example, different Auto-fill configurations, allow unlock with biometrics, etc. But nowhere can I seem to find these settings on the DuckDuckGo Browser – and aside from activating DDG integration in the BW Desktop app prefs there don’t seem to be any other options that control DDG behavior.

When updating a password on a website that has three fields:
– Current password
– New password
– Repeat new password
or equivalent fields, BitWarden for DuckDuckGo fills all three fields with newly generated passwords instead of offering the present password for the first field and generated passwords for the others.

When I am editing passwords in the DDG Browser for Desktop, being logged on to in a browser window, every time I edit a field for a BitWarden entry, BitWarden asks me via pop up in the top right corner if I want to update the password for (i.e., the master password), which I obviously don’t want to.

One of the things that is nice about the DuckDuckGo Browser integration as opposed to the Browser extension in other browsers, is the immediate appearance of the dropdown menu for auto-fill when clicking on a field on any website. However, the prompt shows only the “username” field. Other Browser extensions show both, “name” field and “username” field. It would be nice if this would be the case on DDG too to disambiguate entries for different subdomains of the same website that may use the same username/email, as has been discussed here:

On many websites, including the very
when being prompted to log in again (such as after a reload/refresh) when there is no field for username to be filled, Bitwarden for DuckDuckGo suggest a generated password instead of offering saved ones.

… and fwiw, since we’re at it, two would-be-nice-to-have-s:

When being prompted to save a newly generated password to BitWarden, it would be nice to have the option not only to edit/add a username, but also to edit the name or to modify the URI or add a secondary one.

When being prompted to save a newly generated password to BitWarden, it would be nice to have the option to not create a new one but also to “merge with” or “add to” an existing entry.

I notice that there is no DDG Integration thread in the Beta Forum. I wonder if that means that DDG is entirely responsible for code development and debugging? You might want to document some of these issues in the DDG/iOS repository on GitHub:

Yeah, it’s a mystery where that DDG-BW integration is being developed …
On GitHub there isn’t even a dedicated repository for the DDG Browser … where it would naturally make sense to raise these issues. I’ll wait a bit if anyone else chimes in here with more knowledge of the matter, if not I might ask on the DDG reddit where there seems to be quite some engagement or on the iOS github you linked – at least to figure out where to raise the issues …

The pull request for the DDG-Bitwarden browser integration (PR #1399) was in the DDG/iOS repo that I had linked above, which is why I suggested that as a location to post about these issues.

Per the notes on PR #1399, it seems that DDG devs also uses the platform for discussion, although it is not clear whether that is open to the public or not.

1 Like

Oh, I see, I probably didn’t look carefully on GitHub. That’s good to know, I think that’s probably the place where to post then.

1 Like

On GitHub they suggested to use the feedback form in the DDG Browser so I did that – although there is no way how to follow up with that. I have thus also posted the issues on the DDG Reddit (slightly updated after some more testing).

1 Like