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

Updating 'Why isn't First Party Isolation enabled by default' #106

Open
Sazu-bit wants to merge 1 commit from Sazu-bit/website:sazu-bit-patch-1 into master
pull from: Sazu-bit/website:sazu-bit-patch-1
merge into: librewolf:master
librewolf:master
librewolf:rel
librewolf:webgl
librewolf:changelog
librewolf:astro
First-time contributor
Copy link

Better explanation and further information of First Party Isolation in response to: librewolf/issues#2431

  • Changed "Isolate" to "Isolation"
  • Linked to hacks.mozilla.org for state partitioning (which I think is the most appropriate, review welcomed)
  • Link to more information about Container Tabs directly to support.mozilla.org since LibreWolf doesn't have it's own explanation.
Better explanation and further information of First Party Isolation in response to: https://codeberg.org/librewolf/issues/issues/2431 - Changed "Isolate" to "Isolation" - Linked to hacks.mozilla.org for state partitioning (which I think is the most appropriate, review welcomed) - Link to more information about Container Tabs directly to support.mozilla.org since LibreWolf doesn't have it's own explanation. 
Better explanation and further information of First Party Isolation in response to: librewolf/issues#2431

Thanks, these changes look mostly good to me. For the /containers support link, we should maybe just remove our redirect here? I don't even know why that redirect is there in the first place. The FPI FAQ really doesn't seem to be the appropriate documentation for the "Container Tabs - Learn more" link.

Thanks, these changes look mostly good to me. For the /containers support link, we should maybe just remove our redirect [here](https://codeberg.org/librewolf/support.librewolf.net/src/commit/365b3c1ec7bf6706710345a2864913a79cb67ce4/index.php#L10)? I don't even know why that redirect is there in the first place. The FPI FAQ really doesn't seem to be the appropriate documentation for the "Container Tabs - Learn more" link.
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 sazu-bit-patch-1:Sazu-bit-sazu-bit-patch-1
git switch Sazu-bit-sazu-bit-patch-1

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 Sazu-bit-sazu-bit-patch-1
git switch Sazu-bit-sazu-bit-patch-1
git rebase master
git switch master
git merge --ff-only Sazu-bit-sazu-bit-patch-1
git switch Sazu-bit-sazu-bit-patch-1
git rebase master
git switch master
git merge --no-ff Sazu-bit-sazu-bit-patch-1
git switch master
git merge --squash Sazu-bit-sazu-bit-patch-1
git switch master
git merge --ff-only Sazu-bit-sazu-bit-patch-1
git switch master
git merge Sazu-bit-sazu-bit-patch-1
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
2 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!106
Reference in a new issue
librewolf/website
No description provided.
Delete branch "Sazu-bit/website:sazu-bit-patch-1"

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?