Include LibreWolf in the group of web browsers supported with the correct paths, to avoid having to use the tricks with symlinks from Firefox/Mozilla folder to be able to get proper integration.
Recent librewolf versions should read the same paths as firefox to avoid needing symlinks
As of 148 I still needed it. I would need to recheck.
In that case it looks like the patch broke. It was supposed to work since 140
Sowwyy, I'm a silly idiot 🥴
However, just using the default Firefox paths is fine.
Please don't start using LibreWolf specific paths.
The whole thing is already messy enough with the dozens of different paths.
If it is currently not working with the default Firefox paths, would be great to know which of them you are using at the moment.
https://librewolf.net/docs/faq/#how-do-i-get-native-messaging-to-work
This seems to be still listed in the faq, and is needed for the web browser integration to work.
keepasschi is already populating ~/.mozilla/native-messaging-hosts
keepasschi/keepasschi@d3ea5c1891/src/browser/NativeMessageInstaller.cpp (L70)
LibreWolf does read ~/.mozilla/native-messaging-hosts by its own, no need for symlinks.
librewolf/source#98
If this is not the case for you, please report this at https://codeberg.org/librewolf/issues/issues, since it then would be a bug.
But I use ~/.mozilla/native-messaging-hosts right now, so if that would be broken it should be some edgecase.
Not saying I don't appreciate the effort for LibreWolf-specific support <3
But the whole native-messaging-hosts situation is already messy enough... Like... an application like KeePassXC would need to put the same file into like 30 different paths, just so every fork, variant, or fork of a fork can read the config from its very own path.
LibreWolf does still support its own path, but we don't really expect any application to automatically populate that path.
In fact, if an application were to automatically populate ~/.librewolf/native-messaging-hosts, it would break profile handling for more or less any user who has recently installed LibreWolf.
But thanks for the hint, will update the LibreWolf FAQ.
I tested last version and only had to close LibreWolf before removing the symlink, detected the DB without issues after some seconds. So it works.
Closing as no action is needed.
No due date set.
No dependencies set.
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?