Rule-based Isolation

[stoically]

• Refactor Isolation UI/UX to be more like e.g. Request Control where a rule could consist of cause, origin, target, action
• Merge Global and Per-Domain Isolation preferences
• Make sure all existing isolation preferences are migrated
• Maybe move cookies, scripts, history and "ignored requests" to the rule-editor as well
• Another interesting use case might be the ability to generically edit headers, so it'd e.g. possible to block JS in TCs via CSP (uMatrix and NoScript don't seem to plan to support containers)

[crssi]

Maybe also something like Containerise ?

[stoically]

Could you elaborate what you mean?

[crssi]

Yes... sorry about being too cryptic... had to run out.

I am using Containerise because if a permanent container is defined in it, then click on external link (like in a email client), does really open in a specific permanent container... even when FF initially is closed.
For example, I do open a lot of github stuff from github notifications over email and to avoid to login on every page being in separate containers i have a rule github.com , GITHUB in a Containerise which does the trick.

I just mentioned it, because I am missing this kind of functionality in TC... but it is not essential.
This issue just looked to me as a future todo list, so I mentined. 😄

Thank you @stoically for one of the best extensions out there.

Cheers

[stoically]

I want to avoid adding full-blown permanent container management, but it might actually have a place in the rule-based isolation UI/UX (since e.g. excluding permanent containers is already a thing as well). Have to see how it turns out once some work on it happens.