librewolf/website
14
55
Fork
You've already forked website
39

docs: add caveat when adding search engine through Firefox settings and solve Cookie exceptions auto-removed after restarts mystery #105

Open
Silverbullet069 wants to merge 4 commits from Silverbullet069/librewolf-website:docs/faq-persist-cookie into master
pull from: Silverbullet069/librewolf-website:docs/faq-persist-cookie
merge into: librewolf:master
librewolf:master
librewolf:rel
librewolf:webgl
librewolf:changelog
librewolf:astro
First-time contributor
Copy link
Following [librewolf/issues#2326](https://codeberg.org/librewolf/issues/issues/2326), [Reddit #1](https://www.reddit.com/r/LibreWolf/comments/vxoq4i/librewolf_deleting_my_cookie_exceptions/) [Reddit #2](https://www.reddit.com/r/LibreWolf/comments/1jfylvg/cookies_getting_deleted_even_though_i_added_an/) [Reddit #3](https://www.reddit.com/r/LibreWolf/comments/18c5mr8/librewolf_automatically_removing_exception_and/) [Reddit #4](https://www.reddit.com/r/LibreWolf/comments/1jrprbu/is_librewolf_logging_me_out_of_sites_what_feature/)
Silverbullet069 changed title from (削除) docs: add caveat when adding search engine through Firefox settings and fix Cookie exceptions auto-removed after restarts (削除ここまで) to docs: add caveat when adding search engine through Firefox settings and solve Cookie exceptions auto-removed after restarts mystery 2025年05月05日 18:34:24 +02:00

The docs on the search engine look good to me, but do we have any more information on why permissions.memory_only would be set to true? Afaik, this is set nowhere by LibreWolf. Did you add it manually? If that is the case, I am not sure if this pref specifically should belong in the FAQ. And if it got set accidentally for a subset of LibreWolf users (for whatever reason), just clearing the pref on a new version may be the better solution here.

The docs on the search engine look good to me, but do we have any more information on why `permissions.memory_only` would be set to `true`? Afaik, this is set nowhere by LibreWolf. Did you add it manually? If that is the case, I am not sure if this pref specifically should belong in the FAQ. And if it got set accidentally for a subset of LibreWolf users (for whatever reason), just clearing the pref on a new version may be the better solution here.
Author
First-time contributor
Copy link

@maltejur wrote in #105 (comment):

The docs on the search engine look good to me, but do we have any more information on why permissions.memory_only would be set to true? Afaik, this is set nowhere by LibreWolf. Did you add it manually? If that is the case, I am not sure if this pref specifically should belong in the FAQ. And if it got set accidentally for a subset of LibreWolf users (for whatever reason), just clearing the pref on a new version may be the better solution here.

Ah yes, it's kinda personal to me. I should have update it somewhere else such as Arkenfox.

I will drop the info about permission.memory_only.

@maltejur wrote in https://codeberg.org/librewolf/website/pulls/105#issuecomment-4705542: > The docs on the search engine look good to me, but do we have any more information on why `permissions.memory_only` would be set to `true`? Afaik, this is set nowhere by LibreWolf. Did you add it manually? If that is the case, I am not sure if this pref specifically should belong in the FAQ. And if it got set accidentally for a subset of LibreWolf users (for whatever reason), just clearing the pref on a new version may be the better solution here. Ah yes, it's kinda personal to me. I should have update it somewhere else such as Arkenfox. I will drop the info about `permission.memory_only`.

I think this change is no longer needed since the settings now have the option to define a suggestions endpoint, am I'm correct?

I think this change is no longer needed since the settings now have the option to define a suggestions endpoint, am I'm correct?
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u docs/faq-persist-cookie:Silverbullet069-docs/faq-persist-cookie
git switch Silverbullet069-docs/faq-persist-cookie

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff Silverbullet069-docs/faq-persist-cookie
git switch Silverbullet069-docs/faq-persist-cookie
git rebase master
git switch master
git merge --ff-only Silverbullet069-docs/faq-persist-cookie
git switch Silverbullet069-docs/faq-persist-cookie
git rebase master
git switch master
git merge --no-ff Silverbullet069-docs/faq-persist-cookie
git switch master
git merge --squash Silverbullet069-docs/faq-persist-cookie
git switch master
git merge --ff-only Silverbullet069-docs/faq-persist-cookie
git switch master
git merge Silverbullet069-docs/faq-persist-cookie
git push origin master
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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
librewolf/website!105
Reference in a new issue
librewolf/website
No description provided.
Delete branch "Silverbullet069/librewolf-website:docs/faq-persist-cookie"

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?