Thanks Richard!
Do you think you'll be able to fix bug 988107 soon so that we can ship
this on Firefox OS at the same time as desktop and Android?
Cheers,
Ehsan
On 2014-04-16, 9:30 AM, Richard Barnes wrote:
Primary eng emails
rbar...@mozilla.com, eh...@mozilla.com
Spec
http://www.w3.org/TR/beacon/
*Summary*
Allows pages to send a "beacon" HTTP request. Beacons are allowed a
limited subset of HTTP (only a few content types), and the JS cannot
receive the content of the response. However, beacon requests will
survive after the page is unloaded, removing the need for synchronous
XHRs in onunload handlers.
The specification is currently under development in W3C, but has been
substantially stable for a while.
http://www.w3.org/TR/beacon/
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html
It landed behind a runtime flag in mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=936340
The flag is: beacon.enabled
Nightly is turned on by default.
https://bugzilla.mozilla.org/show_bug.cgi?id=990220
*WebKit:*
We are not aware of implementation effort in WebKit.
*Blink:*
The Chromium team has announced their intent to implement and opened a bug.
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Vdi7F7Mk_rM/L5D9HjNmt8YJ
https://code.google.com/p/chromium/issues/detail?id=360603
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
