Thanks to you both! Can you explain, like you might to a three-year-old, why this is considered a bug?
Well, you are getting forwarded to an issue tracker for technical discussions. The context is people collaborating on the Firefox codebase. In this space, “bug” might not imply what you think it does. Like, new features still under development and general improvements are also tracked as “bugs” in Bugzilla. That doesn’t mean that anything was considered broken.
With regards to where runtime files and data is stored, the Firefox (and therefore Librewolf) way of doing it is widely considered legacy at this point. They probably wouldn’t build it that way if it was done from scratch today. But it comes from a different era. There is now heritage, legacy, and compatibility making the transition take years. That is normal and expected with a project as widely adopted and integrated as Firefox.
I think there is not much unique to Librewolf here (exception might be the librewolf.overrides.cfg); it’s just inheriting and following upstream.
Old place: .librewolf. New place: Split between ~/.config/librewolf (config) and ~/.local/share/librewolf (data).
Here and now as an existing user who doesn’t really want to care, I would advice sticking with the “old” current location of just ~/.librewolf and not moving things around or reconfiguring yourself. It’s still being relied on by some parts of the browser. Depending on what features and addons you use, things might break if you expect to do a full move already.
Some people feel strongly about “stay the F* out of my home directory, all you apps” and they might tell us this really is a Bug, how crazy it is that it isn’t fixed yet, etc. Their concerns aren’t relevant for a three-year old. Or even most people who just want their browser to work. They might actually help in pushing development forward and the platform getting on with the times. And they find and complain about the edge-cases so that step by step the transition becomes more seamless and complete. But bottom line is that calls for action are targeted at devs and maintainers; not users like yourself (really not meant as gate-keeping but more to point out that there’s a depth and assumption of context here making it take some immersion to make sense of what’s being said and choosing not to partake is fine).
Well, you are getting forwarded to an issue tracker for technical discussions. The context is people collaborating on the Firefox codebase. In this space, “bug” might not imply what you think it does. Like, new features still under development and general improvements are also tracked as “bugs” in Bugzilla. That doesn’t mean that anything was considered broken.
With regards to where runtime files and data is stored, the Firefox (and therefore Librewolf) way of doing it is widely considered legacy at this point. They probably wouldn’t build it that way if it was done from scratch today. But it comes from a different era. There is now heritage, legacy, and compatibility making the transition take years. That is normal and expected with a project as widely adopted and integrated as Firefox.
I think there is not much unique to Librewolf here (exception might be the
librewolf.overrides.cfg); it’s just inheriting and following upstream.Old place:
.librewolf. New place: Split between~/.config/librewolf(config) and~/.local/share/librewolf(data).Here and now as an existing user who doesn’t really want to care, I would advice sticking with the “old” current location of just
~/.librewolfand not moving things around or reconfiguring yourself. It’s still being relied on by some parts of the browser. Depending on what features and addons you use, things might break if you expect to do a full move already.See for example https://bugzilla.mozilla.org/show_bug.cgi?id=2005167
Some people feel strongly about “stay the F* out of my home directory, all you apps” and they might tell us this really is a Bug, how crazy it is that it isn’t fixed yet, etc. Their concerns aren’t relevant for a three-year old. Or even most people who just want their browser to work. They might actually help in pushing development forward and the platform getting on with the times. And they find and complain about the edge-cases so that step by step the transition becomes more seamless and complete. But bottom line is that calls for action are targeted at devs and maintainers; not users like yourself (really not meant as gate-keeping but more to point out that there’s a depth and assumption of context here making it take some immersion to make sense of what’s being said and choosing not to partake is fine).