Google Git
Sign in
chromium / external / w3c / web-platform-tests / 92d9bd4ddb7ffe622e8cd4887fd2b405736b891e / . / origin-isolation
tree: ed4b3c539213a7a95bf0c8f3d3d927f35f57cbd4 [path history] [tgz]
  1. 1-iframe/
  2. 2-iframes/
  3. getter-special-cases/
  4. iframe-navigation/
  5. popups/
  6. resources/
  7. about-blank.https.sub.html
  8. about-blank.https.sub.html.headers
  9. document-domain.sub.https.html
  10. document-domain.sub.https.html.headers
  11. going-back.sub.https.html
  12. going-back.sub.https.html.headers
  13. insecure-http.sub.html
  14. insecure-http.sub.html.headers
  15. META.yml
  16. popups-crash.https.html
  17. README.md
  18. removing-iframes.sub.https.html
  19. removing-iframes.sub.https.html.headers
origin-isolation/README.md

Origin isolation tests

These tests are for the proposal at WICG/origin-isolation. They should eventually move into a subdirectory of html/ if/when that proposal merges into the HTML Standard.

Test filenames

The tests in 2-iframes follow the file naming pattern

parent-[yes|no]-child1-[yes|no]-[designator]-child2-[yes|no]-[designator]

Here:

  • yes or no refers to whether the Origin-Isolation header is set or unset.
  • designator explains how the child differs from the parent: e.g. by being a subdomain, or having a different port, or both. There‘s also same if it’s same-origin.

Other directories have variations on this, e.g. 1-iframe/ does the same thing but for a single child instead of child1 and child2, and navigation/ uses 1 and 2 to represent the two different locations the single iframe will be navigated to.

Coverage

Header parsing is covered by a few tests in the 1-iframe/ subdirectory, and not duplicated to all other scenarios.