Firefox's new site isolation feature

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

I just enabled it and have not noticed any difference. Some things that I thought it would impact but has not:

1. I have 3 tabs open, each pointing to a different area of a forum. The forum will add a count of alerts to the tab name, and it shows up on all three, and is cleared on all when the alerts have been viewed from one tab. I thought that with isolation that this info would be localized to the current tab.

2. Similarly, I have two tabs open, one for the general account and another for a discussion area of that account. If I am not signed into the account then the section at the top right of the discussion tab shows "Sign-in". When I sign in on the account page and then do a refresh on the discussion tab it now shows my userID instead of "sign-in".

Anyone have a sample or a link to what it does or prevents?
It's isolating all sites from the same domain (with special exceptions for things like GitHub) into the same process/access space. That means multiple tabs sitting on the same site are all able to work together. It means that sites referenced from the site, or plugins like LastPass, should remain isolated from other sites. Even sites isolated in a tab are not isolated from the site's cookies (same domain) so you shouldn't expect logins on one tab to not reflect on another tab from the same site--doing it any other way would break the way the web works.
I've notice issues with youtube. Videos are slow to start. Not sure if it from having fission active or not.
Is this feature enabled by default in 89.0?

If not how do I enable the feature?