[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13749 [Tor Browser]: Write tests for network.thirdparty.isolate

#13749: Write tests for network.thirdparty.isolate
-----------------------------+----------------------------------
     Reporter:  mikeperry    |      Owner:  arthuredelstein
         Type:  task         |     Status:  assigned
     Priority:  normal       |  Milestone:
    Component:  Tor Browser  |    Version:
   Resolution:               |   Keywords:  TorBrowserTeam201411
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+----------------------------------

Comment (by mikeperry):

 gk - that's true, but I wanted to involve as many aspects of the page
 rendering as possible. The new patch is based on our getFirstPartyURI()
 API. Part of testing this is making sure that API also is behaving sanely
 for iframes, script src, link rel, etc etc.

 I also just realized that we should probably also test Etag isolation as
 part of this. In previous versions of this cache isolation feature, it was
 covered. That may no longer be the case (or it may not be the case when
 the transition to Cache2 is complete).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13749#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs