Automatically associate/start sandboxes with triggers

[madduck]

It would be awesome if I could associate a regexp against URLs with each sandbox such that when I open a tab the first sandbox with a regexp matching the URL will be "applied".

[srgvg]

+1

[dogancelik]

:+1:

Update: I donated to this issue, please support it: https://www.bountysource.com/issues/9291161-automatically-associate-start-sandboxes-with-triggers

I hope I understand correctly, you want to switch between Sandboxes based on URL if a Regex matches. If so, this would be really good.

There should be a new tab inside chrome://priv8/content/manager.xul called "Redirects" or "Redirections" and it should contain a table interface or a text box that contains:

• Sandbox Type (0 or -1 for no sandbox, 1000-n for Sandbox App Ids)
• Url Regex
• (optionally) Applied Sandboxes

Example Redirection table:

Sandbox Type	URL Regex
1005	https?:\/\/(www\.)?facebook\.com.*
1002	https?:\/\/(www\.)?youtube\.com.*

When a user opens a Facebook link, the tab he's in currently will switch to Sandbox 1005, and every Youtube links will open in Sandbox 1002.

An example:

1. I'm on site A (site-a.com) and I click on a link (href is site-b.com)
2. Priv8 detects URL change of tab, checks "Redirection table"
3. If there a Regex match for site-b.com, switch to specified Sandbox for site B

Additional features for Redirection table:

• Every redirection rule should be only applied in selected sandboxes

Sandbox Type	URL Regex	Applied Sandboxes
1005	https?:\/\/(www\.)?facebook\.com.*	1004, 1003
1002	https?:\/\/(www\.)?youtube\.com.*	-1

When user in a Sandbox tab 1004 or 1003 and opens a Facebook link in these sandboxes, tab will switch to Sandbox 1005. This redirection rule will not work in non-sandboxes tabs or other sandboxes (1006, 1007, 1005 etc.)

-1 for Applied Sandboxes means this redirection rule will work for every tab (whether sandboxed or not)

A Stackoverflow question for adding a new protocol: http://stackoverflow.com/questions/1556144/how-do-i-add-protocol-handler-to-firefox-from-extension

[lex-men]

Problem solved?