-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Isolation based on webNavigation.TransitionType #327
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 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. |
This comment has been minimized.
This comment has been minimized.
I updated the Mozilla bug from UNCONFIRMED to NEW so it maybe gets picked up quicker. |
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 thatwebNavigation.onCommitted
has no request id, and hence the decision must be made based on thetabId
.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.
The text was updated successfully, but these errors were encountered: