commit 224f1def4bc73af7752471252f9eef8a13af99a8 Author: Mike Perry mikeperry-git@torproject.org Date: Wed May 6 13:57:52 2015 -0700

Remove mention of third party cache isolation.

The cache is not always isolated for all third parties (only those sourced inside iframes/frames). --- design-doc/design.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/design-doc/design.xml b/design-doc/design.xml index a59e610..eeeb5d1 100644 --- a/design-doc/design.xml +++ b/design-doc/design.xml @@ -1118,7 +1118,7 @@ isolation means that all identifier sources and browser state are scoped (isolated) using the URL bar domain. This scoping is performed in combination with any additional third party scope. When first party isolation is used with explicit identifier storage that already has a constrained third -party scope (such as cookies, DOM storage, and cache), this approach is +party scope (such as cookies and DOM storage), this approach is referred to as "double-keying".

</para>