startup.homepage_welcome_url.additional

[yashxog]

the startup.homepage_welcome_url.additional, app.releaseNotesURL.prompt, app.releaseNotesURL.prompt, pref("app.releaseNotesURL.prompt", "https://zen-browser.app/release-notes/%VERSION%/");
this pref are getting setup in branding/{brand-name}/pref/firefox-branding.js file but I am not understanding from where it is getting assigned those values?

[dosubot[bot]]

The values for startup.homepage_welcome_url.additional and app.releaseNotesURL.prompt are not explicitly detailed in the information I have. However, the dynamic assignment of version numbers in URLs like https://zen-browser.app/release-notes/%VERSION%/ is handled by configuration scripts. Specifically, the src/toolkit/modules/UpdateUtils-sys-mjs.patch file changes the replacement for the "VERSION" placeholder to use AppConstants.ZEN_FIREFOX_VERSION. This constant is defined in the src/toolkit/modules/AppConstants-sys-mjs.patch file, and the version is set using the ZEN_FIREFOX_VERSION environment variable in the src/toolkit/moz-configure.patch file ^[1][2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[dosubot[bot]]

The URL prefix "https://zen-browser.app" is defined or hardcoded in several places within the Zen Browser's codebase. Specifically, it appears in the configuration line in zen-browser.js and in the nsAboutRedirector.cpp file:

1. In zen-browser.js:

   pref('zen.injections.match-urls', 'https://zen-browser.app/*,https://share.zen-browser.app/*', locked);

2. In nsAboutRedirector.cpp:

   {"credits", "https://zen-browser.app/about/",
    nsIAboutModule::URI_SAFE_FOR_UNTRUSTED_CONTENT |
    nsIAboutModule::URI_MUST_LOAD_IN_CHILD},

Additionally, during the build process, the src/build/moz-build.patch file specifies or overrides the URL prefix for the update host, changing it to "updates.zen-browser.app" ^[1][2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[yashxog]

I am not able to find pref('zen.injections.match-urls', 'https://zen-browser.app/*,https://share.zen-browser.app/*', locked); in zen-browser.js,

[dosubot[bot]]

The setting pref('zen.injections.match-urls', 'https://zen-browser.app/*,https://share.zen-browser.app/*', locked); is located in the zen-browser.js file under the #ifdef MOZILLA_OFFICIAL section. If you are not finding it, it might be due to conditional compilation or different build configurations. Ensure that the MOZILLA_OFFICIAL environment variable is set to include this section in the build ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[yashxog]

My fork dont have the above line of code as it added later , But I am asking from where the default tab on opening new profile or after new build automatically sets to https://zen-browser.app/release-notes and (https://zen-browser.app/privacy-policy/) page? as I found that it is been setting up in branding directory but I am finding the origin for this. from where we are sitting up default tabs which gets on new profile or after launching the browser build for the first time

[dosubot[bot]]

The specific configuration for setting default tabs, such as the release notes and privacy policy pages, upon creating a new profile or launching the browser for the first time, is not explicitly detailed in the information I have. However, this behavior is typically configured in the branding directory or through specific configuration files related to the browser's initial setup.

In the Zen Browser, the ZenProfileDialogUI component is responsible for handling initial profile setup, which might include setting default tabs ^[1]. You may want to investigate the ZenProfileDialogUI.mjs file further or look into other configuration files within the branding directory that might specify these default URLs. Additionally, checking for any environment variables or build scripts that influence these settings could provide more insights.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}