Revision 4f06a45252465792447f80b6559b17c4c4e9712c authored by Daniel Vogelheim on 10 April 2018, 13:07:39 UTC, committed by Chromium WPT Sync on 10 April 2018, 13:07:39 UTC
Allow control of the deprecation via runtime enabled features, with a first
step for logging a warning to the console, and the second step to block it
outright.
Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ
Change-Id: I1be1001cbbef152458119b1516750bb4f1d1e4de
Reviewed-on: https://chromium-review.googlesource.com/975611
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549495}
1 parent 069680c
open-referer.htm
<!doctype html>
<html>
<head>
<title>XMLHttpRequest: open() - value of Referer header</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<link rel="help" href="https://xhr.spec.whatwg.org/#the-open()-method">
</head>
<body>
<div id="log"></div>
<script>
test(function() {
var client = new XMLHttpRequest()
client.open("POST", "resources/inspect-headers.py?filter_name=referer", false)
client.send(null)
assert_equals(client.responseText, "Referer: "+location.href+'\n')
})
</script>
</body>
</html>
Computing file changes ...
