celenity/Phoenix
8
198
Fork
You've already forked Phoenix
18

[ENHANCEMENT] Create a custom onboarding #290

Open
opened 2026年05月17日 23:49:19 +02:00 by celenity · 6 comments

Due to recent changes in Phoenix’s structure/design, it’s now finally viable for us to create an onboarding so that users can configure important settings/behavior (ex. like we have for IronFox).

Creating this issue to keep track of progress on this and what needs to be done.

If anyone has any suggestions for preferences/behavior we should add to the onboarding, please share them here!

Due to recent changes in Phoenix’s structure/design, it’s now finally viable for us to create an onboarding so that users can configure important settings/behavior *(ex. like we have for IronFox)*. Creating this issue to keep track of progress on this and what needs to be done. If anyone has any suggestions for preferences/behavior we should add to the onboarding, please share them here!

I wasn't sure what is meant by onboarding in this context, but if you mean the toggles to enable/disable settings in the Ironfox settings options, many of the same found there would be useful in FF, for starters.

One idea might be to also include access (with edit capability) to phoenix-specialized.cfg from inside FF, assuming 1. it would pose no security risk and 2. it would not be incredibly difficult to develop (I've little idea about effort required).

Also a direct 1-click link to opening of about:config into a new tab might be useful (to adjust phoenix settngs). Obviously these are fluffy suggestions but if the effort to produce this kind of functionality is not great, it would be kind of nice to have this menu page function as a sort of main control-panel for different aspects of phoenix settings in FF.

I wasn't sure what is meant by onboarding in this context, but if you mean the toggles to enable/disable settings in the `Ironfox settings` options, many of the same found there would be useful in FF, for starters. One idea might be to also include access (with edit capability) to `phoenix-specialized.cfg` from inside FF, assuming 1. it would pose no security risk and 2. it would not be incredibly difficult to develop (I've little idea about effort required). Also a direct 1-click link to opening of about:config into a new tab might be useful (to adjust phoenix settngs). Obviously these are fluffy suggestions but if the effort to produce this kind of functionality is not great, it would be kind of nice to have this menu page function as a sort of main control-panel for different aspects of `phoenix` settings in FF.
Contributor
Copy link

@GW72 wrote in #290 (comment):

onboarding

I think that means starter/initial screen/setup.

@GW72 wrote in https://codeberg.org/celenity/Phoenix/issues/290#issuecomment-15799358: > onboarding I think that means starter/initial screen/setup.
Author
Owner
Copy link

@GW72 wrote in #290 (comment):

I wasn't sure what is meant by onboarding in this context

Yeah, @koru is correct - what I mean by onboarding here is an initial set-up (similar to the onboarding on stock Firefox, and IronFox on mobile). So the goal would be for it to cover important/commonly overridden settings by users.

To start at least, similar to IronFox's onboarding, I think I'll definitely add DoH-related settings and locale spoofing.

but if you mean the toggles to enable/disable settings in the Ironfox settings options, many of the same found there would be useful in FF, for starters.

Unfortunately, I don't think there's currently a way we can implement a custom settings panel like this directly, though it would be nice if we could. It'd probably be possible if we disabled the AutoConfig sandbox, but I'm not particularly comfortable with that from a privacy and security perspective.

One idea might be to also include access (with edit capability) to phoenix-specialized.cfg from inside FF, assuming 1. it would pose no security risk and 2. it would not be incredibly difficult to develop (I've little idea about effort required).

I don't think this would be possible either, for similar reasons.

Also a direct 1-click link to opening of about:config into a new tab might be useful

This might be possible - at least we could probably add it as a default bookmark or pin it to the browser homepage by default. I think it may be worth adding about:support as well.

Thank you for sharing your ideas/suggestions here! Much appreciated as always.

@GW72 wrote in https://codeberg.org/celenity/Phoenix/issues/290#issuecomment-15799358: > I wasn't sure what is meant by onboarding in this context Yeah, @koru is correct - what I mean by onboarding here is an initial set-up *(similar to the onboarding on stock Firefox, and IronFox on mobile)*. So the goal would be for it to cover important/commonly overridden settings by users. To start at least, similar to IronFox's onboarding, I think I'll definitely add DoH-related settings and locale spoofing. > but if you mean the toggles to enable/disable settings in the `Ironfox settings` options, many of the same found there would be useful in FF, for starters. Unfortunately, I don't *think* there's currently a way we can implement a custom settings panel like this directly, though it would be nice if we could. It'd probably be possible if we disabled the AutoConfig sandbox, but I'm not particularly comfortable with that from a privacy and security perspective. > One idea might be to also include access (with edit capability) to `phoenix-specialized.cfg` from inside FF, assuming 1. it would pose no security risk and 2. it would not be incredibly difficult to develop (I've little idea about effort required). I don't think this would be possible either, for similar reasons. > Also a direct 1-click link to opening of about:config into a new tab might be useful This might be possible - at least we could probably add it as a default bookmark or pin it to the browser homepage by default. I think it may be worth adding `about:support` as well. Thank you for sharing your ideas/suggestions here! Much appreciated as always.

Thanks for the clarifications!

A bit off topic perhaps, but couldn't you simply make a phoenix browser based on FF, in the same spirit as ironfox? Again, this could require an enormous effort (and pose licensing issues???), I've no idea, but would that not solve a few problems?

Thanks for the clarifications! A bit off topic perhaps, but couldn't you simply make a `phoenix browser` based on FF, in the same spirit as `ironfox`? Again, this could require an enormous effort (and pose licensing issues???), I've no idea, but would that not solve a few problems?

@celenity is the browser.preonboarding.enabled change from defaultPref() in 2026年04月27日.1 to user pref() in 2026年05月21日.2 related to this? will phoenix (somehow?) use the about:welcome modal for onboarding?

@celenity is the `browser.preonboarding.enabled` change from [`defaultPref()` in 2026年04月27日.1](https://codeberg.org/celenity/Phoenix/src/tag/2026.04.27.1/linux/phoenix.cfg#L347) to [`user pref()` in 2026年05月21日.2](https://codeberg.org/celenity/Phoenix/src/tag/2026.05.21.2/phoenix-unified.cfg#L440) related to this? will phoenix (somehow?) use the about:welcome modal for onboarding?
Author
Owner
Copy link

@degausser wrote in #290 (comment):

@celenity is the browser.preonboarding.enabled change from defaultPref() in 2026年04月27日.1 to user pref() in 2026年05月21日.2 related to this?

No, that actually looks like a mistake - will fix for next release, thank you for catching this!

will phoenix (somehow?) use the about:welcome modal for onboarding?

Yes, that is the intention. My understanding is we can customize its contents with the browser.aboutwelcome.screens pref.

@degausser wrote in https://codeberg.org/celenity/Phoenix/issues/290#issuecomment-15908477: > @celenity is the `browser.preonboarding.enabled` change from [`defaultPref()` in 2026年04月27日.1](https://codeberg.org/celenity/Phoenix/src/tag/2026.04.27.1/linux/phoenix.cfg#L347) to [`user pref()` in 2026年05月21日.2](https://codeberg.org/celenity/Phoenix/src/tag/2026.05.21.2/phoenix-unified.cfg#L440) related to this? No, that actually looks like a mistake - will fix for next release, thank you for catching this! > will phoenix (somehow?) use the about:welcome modal for onboarding? Yes, that is the intention. My understanding is we can customize its contents with the `browser.aboutwelcome.screens` pref.
Sign in to join this conversation.
No Branch/Tag specified
dev
pages
2026年07月08日.1
2026年06月10日.1
2026年05月21日.2
2026年05月21日.1
2026年04月27日.1
2026年03月31日.1
2026年03月30日.1
2026年02月23日.1
2026年02月16日.1
2026年01月21日.1
2025年12月23日.1
2025年11月27日.1
2025年11月07日.1
2025年10月26日.1
2025年10月12日.1
2025年10月03日.1
2025年09月07日.1
2025年08月06日.1
2025年07月30日.1
2025年07月11日.1
2025年06月24日.1
2025年06月12日.1
2025年06月10日.1
2025年06月06日.1
2025年06月02日.2
2025年06月02日.1
2025年05月11日.1
2025年04月27日.1
2025年04月15日.1
2025年04月11日.1
2025年04月02日.1
2025年03月25日.1
2025年03月20日.1
2025年03月12日.1
2025年03月05日.1
2025年02月28日.1
2025年02月21日.1
2024年02月18日.1
2025年02月14日.1
2025年02月13日.1
2025年02月01日.1
2025年01月30日.1
2025年01月27日.1
2025年01月24日.1
2025年01月22日.2
2025年01月22日.1
2025年01月20日.2
2025年01月20日.1
2025年01月19日.1
2025年01月14日.1
2025年01月13日.1
2025年01月12日.2
2025年01月12日.1
2025年01月06日.1
05January2025v1
20240103.2
20250103.1
20241229-1
20241225-1
20241216-1
20241211-1
20241204-1
20241203-1
31November2024v1
20241103-1
20240924-1
20240914-1
20240907-1
20240902-1
20240831-1
20240825-1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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#290
Reference in a new issue
celenity/Phoenix
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?