Skip to content

Add support for DDG ext device type - #8259

Draft
kspearrin wants to merge 1 commit into
mainfrom
ddg-browser
Draft

Add support for DDG ext device type#8259
kspearrin wants to merge 1 commit into
mainfrom
ddg-browser

Conversation

@kspearrin

@kspearrin kspearrin commented Aug 26, 2026

Copy link
Copy Markdown
Member

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-42510

📔 Objective

Adds DeviceType.DuckDuckGoExtension = 27 so DuckDuckGo can be identified as a browser
extension client.

DuckDuckGo now exposes itself as a browser brand — DuckDuckGo appears in
navigator.userAgentData.brands in both popup and service-worker contexts, and they set
matching sec-ch-ua headers during regular browsing. The browser variant
(DuckDuckGoBrowser = 26) already landed and covers the web vault case; this adds the
missing extension variant.

Without it, a DDG extension client has no accurate device type to report and falls back to
ChromeExtension, mislabeling the device in device lists, new-device-login emails, 2FA
emails, and TDE login-approval prompts.

📸 Screenshots

n/a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant