Let's use this bug to track adding WPT coverage for XSDB:
- Listing test ideas and figuring out what is testable
- Figuring out the process of adding tests (especially when XSDB is not yet present in any official spec).
Some test ideas:
- text/css response with a JSON parser breaker should not be blocked
- jpeg served as text/html should not be blocked (thanks to sniffing)
Also - note that many properties of XSDB might not be testable via WPT, because XSDB should be mostly transparent/invisible to the web features.
I'd say that at this point we have sufficient WPT coverage that shouldn't anymore block spec and Blink intent discussions. Adding remaining coverage can be treated as lower the priority. The remaining coverage is mostly needed around sniffing and json security prefix handling.
We might also try to add WPT coverage for link/prefetch (ensuring that CORB blocking doesn't prevent prefetch from populating a browser-side [non-renderer-process] caache). Nick's first unsuccessful attempt at writing this test is at https://crrev.com/c/1033814
Comment 1 by lukasza@chromium.org
, Feb 5 2018