On Mon, Jan 28, 2019 at 12:57 AM Andrea Marchesini <amarches...@mozilla.com> wrote:
> If we try to apply the new cookie policy immediately, 3rd party trackers > in opened tabs should switch to a first-party-isolation storage, but they > could also have already data in memory (user-tokens), and populate the new > cookie jar consequentially. This would break the isolation. The solution in > this case, is to apply the change only after the reloading. > That's a great point in favor of your proposal. I'm still concerned about "infinite-page" sites (facebook/twitter/etc) where a user typically rarely reloads. Would it be too ugly to apply an infobar to each active tab that says "The cookie policy has changed. Reload to apply the new policy [Reload]"? Or maybe has a [Reload this tab][Reload All] set of buttons. I have serious misgivings about my UX suggestion here, but maybe it will spark better ideas on how to communicate to users. An alert/doorhanger in the pref page where the setting is changed that warns the user it only applies to new pages and offers to reload all active tabs? -Dan Veditz _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
