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
We are working on a number of optimizations to Session Restore for Firefox 25 (or 26). To perform one major optimization, we will need to get rid of the state string attached to "sessionstore-state-write" that you are currently using.
We need to find a way to ensure that this will not break Private Tab.
I have the feeling that if:
we keep sending "sessionstore-state-write" but without a nsISupportsString;
we don't save tabs that have attribute usePrivateBrowsing.
This will be sufficient to ensure that your add-on does not break and does not lose features. Could you confirm?
The text was updated successfully, but these errors were encountered:
Yes, I use "sessionstore-state-write" notification only to remove tabs with "privateTab-isPrivate" attribute from session data (because I don't have real tabs here). And only tabs with nsILoadContext.usePrivateBrowsing flag have that DOM attribute.
So, if you filter out all private tabs for me, I don't need "sessionstore-state-write" notification at all.
Hi,
We are working on a number of optimizations to Session Restore for Firefox 25 (or 26). To perform one major optimization, we will need to get rid of the state string attached to
"sessionstore-state-write"
that you are currently using.We need to find a way to ensure that this will not break Private Tab.
I have the feeling that if:
"sessionstore-state-write"
but without ansISupportsString
;usePrivateBrowsing
.This will be sufficient to ensure that your add-on does not break and does not lose features. Could you confirm?
The text was updated successfully, but these errors were encountered: