beacon-frame.html |
Inner frame performing a basic sendBeacon from within an iframe |
646 |
beacon-handler.sjs |
|
4407 |
beacon-originheader-handler.sjs |
TestSever customized specifically for the needs of:
Bug 1280692 - navigator.sendBeacon() should not send origin header
|
1295 |
beacon-preflight-handler.sjs |
|
1222 |
beacon-redirect-handler.sjs |
TestSever customized specifically for the needs of:
Bug 1280692 - sendBeacon() should follow 30x redirect
Here is a sequence of the test:
[1] sendBeacon (identified by the queryString 'beacon') which gets redirected
[2] redirected sendBeacon (identified by the queryString 'redirected') which
updates the state idniciating that redirected sendBeacon succeeds.
[3] xhr request (identified by the queryString 'verifyRedirectDidSucceed')
which checks if the state was not changed from 'reset' to 'gree'. If the channel
woulnd't be blocked correctly the redirected channel would set the state to 'red'.
|
1645 |
beacon-set-cookie.sjs |
|
318 |
chrome.toml |
|
316 |
file_beaconCookies.html |
|
239 |
file_beaconSafelist.html |
|
332 |
mochitest.toml |
|
600 |
test_beacon.html |
Test whether sendBeacon fails for non-HTTP URIs and syntactically incorrect calls |
1445 |
test_beaconContentPolicy.html |
Test that sendBeacon obeys content policy directives |
3540 |
test_beaconCookies.html |
Test whether sendBeacon sets cookies |
2579 |
test_beaconFrame.html |
Test for beacon |
3377 |
test_beaconOriginHeader.html |
Bug 1280692 - navigator.sendBeacon() should send origin header |
2222 |
test_beaconPreflightWithCustomContentType.html |
Test for Bug 1210302 |
1695 |
test_beaconRedirect.html |
Bug 1280692 - sendBeacon() should follow 30x redirect |
1789 |
test_beaconWithSafelistedContentType.html |
Test for Bug 1557386 |
3301 |