1725011 - Add $XDG_CONFIG_HOME handling to firefox-profile-js

Status: RESOLVED FIXED

(Core :: XPCOM, enhancement)

Description

[:gerard-majax]

Before we can land bug 259356, we might need to ensure third-party tooling are updated.

https://github.com/saadtazi/firefox-profile-js/blob/08a4e4cefcb5f023ad6f10e9d869c812b59fa9af/lib/profile_finder.js#L10-L24

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Comment 2

[Shmerl]

Any progress on this?

Comment 3

[:gerard-majax]

No.

Comment 4

[jr.om]

Fix will be released on version 4.6.0 of firefox-profile-js, but its already available on master. See linked issue https://github.com/saadtazi/firefox-profile-js/issues/136. Feedback and testing are welcome.

Are there relevant components within Firefox's code that need to be updated as well, or just the linked repo is enough?

Comment 5

[:gerard-majax]

No, if I am reading right https://github.com/saadtazi/firefox-profile-js/pull/139/files#diff-de699942ceab36681f2eba06c7cbd4ed956ca9291f8761fdedbf7171260d1ba8R36 your fix will make sure we can source data from ~/.config/mozilla/firefox/, which adding support for into firefox-profile-js was what this bug was about.

Comment 6

[:gerard-majax]

If you can verify that my reading is correct, then we can mark this bug as RESOLVED.

Comment 7

[jr.om]

Yes, your reading is correct. The new algorithm searches, in this order, for sandboxed locations (assuming wrongly configured snap/flatpak), then the current dotdir and defaults to the xdg-config dir. (just to be clear, I'm not the author of the PR)

Comment 8

[:gerard-majax]

Thanks!