Re: [w3ctag/design-reviews] Portals (#331)

Thanks for the feedback @othermaciej. I completely agree with you that browsers that already support tracking protection through a storage API should continue to do so inside a portal. In fact, this is something we have described in the [explainer](https://github.com/WICG/portals/blob/master/design-discussion.md#constraint-2).

That said, as you mentioned, Chrome does not currently have any built-in tracking protection, and given that our implementation is on top of Chromium, we are trying to keep our scope manageable, so we are not tackling the storage access just yet on our implementation.

At this point, our main focuses are:
* Solving the origin attribution problem.
* Providing a richer API that allows developers to implement faster navigations and more interesting page transitions.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/331#issuecomment-462454955