bug(beacon): Uncaught DOMException

[ungoldman]

Looks like beacon code merged in #10 fails on chrome:

Uncaught DOMException: Failed to execute 'sendBeacon' on 'Navigator': sendBeacon() with a Blob whose type is not any of the CORS-safelisted values for the Content-Type request header is disabled temporarily. See http://crbug.com/490015 for details.
    at nanobeacon (https://choo.io/bundle.js:85:178)
    at https://choo.io/bundle.js:3:1916

[yoshuawuyts]

Oh yeah, that's new in Chrome 60 which was introduced this week. Oops; should be an open issue on nanobeacon somewhere anticipating this

…

On Fri, Aug 11, 2017, 01:55 Nate Goldman ***@***.***> wrote: Looks like beacon code merged in #10 <#10> fails on chrome: Uncaught DOMException: Failed to execute 'sendBeacon' on 'Navigator': sendBeacon() with a Blob whose type is not any of the CORS-safelisted values for the Content-Type request header is disabled temporarily. See http://crbug.com/490015 for details. at nanobeacon (https://choo.io/bundle.js:85:178) at https://choo.io/bundle.js:3:1916 [image: screen shot 2017-08-10 at 4 54 21 pm] <https://user-images.githubusercontent.com/427322/29196941-940ec774-7dec-11e7-8f06-a0a6f9c277cb.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#16>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWleiN2OnDqRbymq7NMvg_CepjQh4Ujks5sW5hjgaJpZM4O0HPp> .

[yoshuawuyts]

Should be fixed!