You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Private browsing mode doesn't currently get special treatment.
There are two major aspects to consider: 1) the whitelist, and 2) the allowed/blocked request information maintained internally so that RequestPolicy knows what to show in the menu.
I think the easiest thing to do that could be considered expected behavior would be to have anything added to the whitelist during private browsing be temporary and have leaving private browsing mode remove all temporarily whitelisted items.
The internally maintained request data is harder to deal with. One option would be to make a copy of internal data when entering private browsing mode and restore that copy when leaving.
The text was updated successfully, but these errors were encountered:
Fixed in r276. The way we support private browsing is to only allow temporary whitelisting from the menu during private browsing mode and then clearing the temporary whitelist when leaving private browsing. We'll need to make sure to keep private browsing mode in mind when adding functionality like more debug and request logging, as that info would need to be cleared when leaving private browsing mode.
Private browsing mode doesn't currently get special treatment.
There are two major aspects to consider: 1) the whitelist, and 2) the allowed/blocked request information maintained internally so that RequestPolicy knows what to show in the menu.
I think the easiest thing to do that could be considered expected behavior would be to have anything added to the whitelist during private browsing be temporary and have leaving private browsing mode remove all temporarily whitelisted items.
The internally maintained request data is harder to deal with. One option would be to make a copy of internal data when entering private browsing mode and restore that copy when leaving.
The text was updated successfully, but these errors were encountered: