| OLD | NEW |
| 1 CONSOLE WARNING: line 27: Synchronous XMLHttpRequest on the main thread is depre
cated because of its detrimental effects to the end user's experience. For more
help, check https://xhr.spec.whatwg.org/. | 1 CONSOLE WARNING: line 22: Synchronous XMLHttpRequest on the main thread is depre
cated because of its detrimental effects to the end user's experience. For more
help, check https://xhr.spec.whatwg.org/. |
| 2 CONSOLE WARNING: line 27: Synchronous XMLHttpRequest on the main thread is depre
cated because of its detrimental effects to the end user's experience. For more
help, check https://xhr.spec.whatwg.org/. | |
| 3 Test that a 404 response for manifest results in cache removal. | 2 Test that a 404 response for manifest results in cache removal. |
| 4 | 3 |
| 5 Frame 1: Manifest is still available, so a new master resource is added to the c
ache. | 4 Frame 1: Manifest is still available, so a new master resource is added to the c
ache. |
| 6 Frame 2: Manifest loading results in 404 response, so the cache group becomes ob
solete, and an obsolete event is dispatched (because the document in frame was a
ssociated with a cache in the group). | 5 Frame 2: Manifest loading results in 404 response, so the cache group becomes ob
solete, and an obsolete event is dispatched (because the document in frame was a
ssociated with a cache in the group). |
| 7 Frame 3: Manifest is still 404 - the document is never associated with a cache. | 6 Frame 3: Manifest is still 404 - the document is never associated with a cache. |
| 8 Frame 4: Manifest is now available, so the document gets associated with a cache
in a newly created group; the obsolete cache group is not affected. | 7 Frame 4: Manifest is now available, so the document gets associated with a cache
in a newly created group; the obsolete cache group is not affected. |
| 9 Should say SUCCESS: | 8 Should say SUCCESS: |
| 10 | 9 |
| 11 SUCCESS | 10 SUCCESS |
| 12 | 11 |
| OLD | NEW |