Revision 6a53accb3f4093ae4cd2dc8f7a086cd33c0b947f authored by Chris Nardi on 19 March 2018, 18:03:21 UTC, committed by Chris Nardi on 19 March 2018, 18:03:21 UTC
https://github.com/w3c/fxtf-drafts/issues/231 was resolved by allowing this grammar in the spec.
1 parent 730eca9
beacon-redirect.window.js
// META: script=/common/utils.js
// META: script=beacon-common.sub.js
"use strict";
// Execute each sample test per redirect status code.
// Note that status codes 307 and 308 are the only codes that will maintain POST data
// through a redirect.
[307, 308].forEach(function(status) {
// Implement the self.buildId extension to identify the parameterized
// test in the report.
self.buildId = function(baseId) {
return `${baseId}-${status}`;
};
// Implement the self.buildTargetUrl extension to inject a redirect to
// the sendBeacon target.
self.buildTargetUrl = function(targetUrl) {
return `/common/redirect.py?status=${status}&location=${encodeURIComponent(targetUrl)}`;
};
runTests(sampleTests);
});
done();
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...