Run all existing tests with OOR-CORS and Servicified Service Worker enabled,
https://chromium-review.googlesource.com/c/chromium/src/+/1163547,
and classify failure cases (layout test failures are ignored this time, since we have tracked them in virtual tests).
https://docs.google.com/document/d/1H6K5zjosoVWjQunO1tDSAzv6dlu5Vg0hJ3fZQua2_d0/edit?usp=sharing
In short, all failed tests can be roughly classified into following cases. First two cases dominate.
- CORS requests from Chrome Extensions are blocked unexpectedly
- Polymer load fails and can not start testing (html import related?)
- File access is blocked unexpectedly
- CORS requests from PPAPI are blocked unexpectedly
- Unknown timeout (needs further investigation)
- CORS related flag does not work
+ CORS disabler (--disable-web-sercurity)
+ File access enabler (--allow-file-access)
- CHECK failures
+ in CORSURLLoader redirect logic
+ IO thread check
- RANGE header is not permitted by CORS
- Save-Data header disappears in SW
- Different net error (ERR_ABORTED vs ERR_FAILED)
- unexpected network request completion
- failures due to Servicified Service Worker (we'll ignore them at this moment)
"Different net error (ERR_ABORTED vs ERR_FAILED)" comes from mojo connection between CORSURLLoader and network::URLLoader (or MojoAsyncResourceHandler). I'll fix the issue.
The first one will be fixed by 870172.
I will investigate more clear reason why the second case, Polymer load failures, happens to file another dedicated bug for that.
Other cases look minor issues, only a few tests failing.
Polymer failure cases was due to import failures from chrome:// scheme.
Scheme whitelist may fix this issue too, or need something additional for html import. I will work on whitelist impl. first.
Comment 1 by yhirano@chromium.org
, Aug 2Blocking: 736308