sendBeacon should throw a TypeError on bad URLs |
||||||
Issue descriptionDiscussion: https://github.com/w3c/web-platform-tests/pull/4024#discussion_r84792665 Spec update: https://github.com/w3c/beacon/commit/ff26009247cc3c76eb9c7b33cd9185082cff0a01 What is the expected output? navigator.sendBeacon("bad://url") # should throw a TypeError, same as Fetch API.
,
Apr 12 2017
Perhaps Takeshi, or someone else on the Tokyo team? They've been looking at Fetch + sendBeacon stuff as of late.
,
Apr 13 2017
,
Apr 13 2017
Submitted this patch for the change https://codereview.chromium.org/2818563004/
,
Apr 14 2017
,
Apr 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0cfcab89310f8e7ad6db537c686200c0f545b613 commit 0cfcab89310f8e7ad6db537c686200c0f545b613 Author: nikhil.sahni <nikhil.sahni@samsung.com> Date: Tue Apr 18 09:10:57 2017 sendBeacon should throw a TypeError on bad URLs. sendBeacon should throw a TypeError on bad URLs instead of syntax error. Bug= 660241 Review-Url: https://codereview.chromium.org/2818563004 Cr-Commit-Position: refs/heads/master@{#465183} [modify] https://crrev.com/0cfcab89310f8e7ad6db537c686200c0f545b613/third_party/WebKit/LayoutTests/fast/beacon/beacon-basic-expected.txt [modify] https://crrev.com/0cfcab89310f8e7ad6db537c686200c0f545b613/third_party/WebKit/LayoutTests/virtual/sharedarraybuffer/fast/beacon/beacon-basic-expected.txt [modify] https://crrev.com/0cfcab89310f8e7ad6db537c686200c0f545b613/third_party/WebKit/Source/modules/beacon/NavigatorBeacon.cpp
,
Apr 18 2017
Thank you nikhil.sahni@.
,
Apr 18 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tdres...@chromium.org
, Apr 12 2017