Revision c26bdad5f6e564f0a791c746c549493c6f9dae7a authored by andypaicu@chromium.org on 16 August 2017, 15:22:43 UTC, committed by Chromium WPT Sync on 16 August 2017, 15:22:43 UTC
Modified resource fetching to allow piping back to the ResourceClient a struct needed for firing the securityviolationevent. This allows us to specify the targeted element as well in the event. CSP violation events have overly vague srcElement and path when being triggered for an element that requires a fetch because the element is not being passed down to where the csp check takes place and the report is fired. Bug: 737647 Change-Id: I944ea2ea69447c612c01b9e6f723f110fa28a1f5 Reviewed-on: https://chromium-review.googlesource.com/558917 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> WPT-Export-Revision: 31f217e45648ca2ab02d5c681cde6e48f0134852
1 parent 2a86707
| File | Mode | Size |
|---|---|---|
| resources | ||
| compile_worker.js | -rw-r--r-- | 294 bytes |
| create_multiple_memory.worker.js | -rw-r--r-- | 538 bytes |
| incrementer.wasm | -rw-r--r-- | 46 bytes |
| wasm_indexeddb_test.html | -rw-r--r-- | 611 bytes |
| wasm_indexeddb_test.js | -rw-r--r-- | 2.4 KB |
| wasm_local_iframe_test.html | -rw-r--r-- | 683 bytes |
| wasm_serialization_tests.html | -rw-r--r-- | 309 bytes |
| wasm_serialization_tests.js | -rw-r--r-- | 590 bytes |
| wasm_serialization_worker.js | -rw-r--r-- | 580 bytes |
| wasm_service_worker_test.https.html | -rw-r--r-- | 1021 bytes |
Computing file changes ...
