[BUG] In policies.json, search engine aliases shouldn't be comma-separated strings #226

Closed
opened 2026-01-12 21:48:02 +01:00 by degausser · 1 comment

Confirmation Checklist

What web browser(s) are you using with Phoenix?

Firefox

Other

No response

What operating system(s) are you experiencing this issue on?

Ubuntu, Windows

Other

No response

What version of Firefox/Gecko and Phoenix are you using?

Firefox 146.0.1 (Phoenix: 2025.12.23.1)

If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on?

No response

Does the issue occur on a new browser profile?

  • Yes
  • No

Please share your browser's distribution ID.

No response

Please share your browser's update channel.

release

Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed.

(Phoenix defaults)

Firefox Multi-Account Containers
uBlock Origin (Phoenix default lists)

Please explain the issue you are experiencing.

"Alias": "@duckduckgo, @ddg",

"Alias": "@duckduckgonoai, @ddgnoai",

"Alias": "@duckduckgohtml, @ddghtml",

"Alias": "@duckduckgolite, @ddglite",

"Alias": "@startpage, @sp",

"Alias": "@startpageeu, @speu",

these mean the whole string is the search engine alias, not two distinct aliases, which i assume was the intention. the mozilla policy docs refer to the alias field as a keyword to use for the engine (singular). the "alias" after the comma doesn't work, and tabbing in urlbar autocompletes the whole string (e.g. '@duckduckgohtml, @ddghtml'), not just the first keyword.

@celenity preferably only one alias per search engine should be kept (ideally the short form).

Please provide detailed steps to reproduce the issue.

  • attempt to use any short-form search engine aliases from the abovementioned list, for example @ddg, or @sp
  • short form can't be used as an alias on its own, long form tab-completes the whole string
### Confirmation Checklist - [x] I confirm that this issue occurs on the **latest release** of Phoenix. You can check what the latest version is on [the `Releases` page](https://codeberg.org/celenity/Phoenix/releases). - [x] I confirm that this issue has **NOT** already been reported on [the Codeberg issue tracker](https://codeberg.org/celenity/Phoenix/issues), [the GitLab issue tracker](https://gitlab.com/celenityy/Phoenix/-/issues), **and/or** [the GitHub issue tracker](https://github.com/celenityy/Phoenix/issues). ### What web browser(s) are you using with Phoenix? Firefox ### Other _No response_ ### What operating system(s) are you experiencing this issue on? Ubuntu, Windows ### Other _No response_ ### What version of Firefox/Gecko and Phoenix are you using? Firefox 146.0.1 (Phoenix: 2025.12.23.1) ### If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on? _No response_ ### Does the issue occur on a new browser profile? - [x] Yes - [ ] No ### Please share your browser's distribution ID. _No response_ ### Please share your browser's update channel. release ### Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed. (Phoenix defaults) Firefox Multi-Account Containers uBlock Origin (Phoenix default lists) ### Please explain the issue you are experiencing. https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L23 https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L32 https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L41 https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L50 https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L81 https://codeberg.org/celenity/Phoenix/src/commit/f09568c8a71af4fe42dd43c6f711c67daf605f1e/build/policies/phoenix-unified.json#L90 these mean _the whole string_ is the search engine alias, not two distinct aliases, which i assume was the intention. the mozilla policy docs refer to the alias field as [a keyword to use for the engine](https://mozilla.github.io/policy-templates/#searchengines--add:~:text=Alias%20is%20a%20keyword%20to%20use%20for%20the%20engine) _(singular)_. the "alias" after the comma doesn't work, and tabbing in urlbar autocompletes the whole string (e.g. `'@duckduckgohtml, @ddghtml'`), not just the first keyword. @celenity **preferably only one alias per search engine should be kept _(ideally the short form)_.** ### Please provide detailed steps to reproduce the issue. - attempt to use any short-form search engine aliases from the abovementioned list, for example `@ddg`, or `@sp` - short form can't be used as an alias on its own, long form tab-completes the whole string
Owner

Good catch, thank you for finding and reporting this!

Good catch, thank you for finding and reporting this!
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
celenity/Phoenix#226
No description provided.