Temporary-containers: Isolation based on webNavigation.TransitionType

Created on 15 Nov 2019  路  6Comments  路  Source: stoically/temporary-containers

Would need the webNavigation permission, though that could be asked on-demand. The list of transition types can be found here. That might be useful to e.g. only trigger isolation when the user entered something into the address bar. The only issue might be that webNavigation.onCommitted has no request id, and hence the decision must be made based on the tabId.

When/If implementing that, it might be worthwhile to consider changing the (Per Domain) Isolation UI to be more like something like Request Control's Rules.

enhancement firefox api limitation

Most helpful comment

Here's the ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1600069

Putting this issue in the blocked by third-party column for now.

All 6 comments

That is so thrilling. Cannot wait for it. Christmas is coming. 馃槃 馃憤

Welp, sorry to get you hyped @crssi, but it seems I was wrong. While the feature could be implemented, it wouldn't prevent the tab from actually connecting to the remote server (and potentially sending cookies), since the webNavigation.onCommitted docs say At least part of the new document has been received from the server.

I'll look into opening a bugzilla ticket and ask for the needed API changes.

If you open the bugzilla ticket then, please, make sure you post it here, so I/we can place a vote on bugzilla. 馃槈

Thank you

Here's the ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1600069

Putting this issue in the blocked by third-party column for now.

Voted 馃槃

I updated the Mozilla bug from UNCONFIRMED to NEW so it maybe gets picked up quicker.

Was this page helpful?
0 / 5 - 0 ratings