On Wed, Apr 16, 2014 at 7:52 AM, Benjamin Smedberg
wrote:
> On 4/16/2014 9:30 AM, Richard Barnes wrote:
>> 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,
On 2014-04-16, 5:50 PM, Gavin Sharp wrote:
The question was simply "are there non-tracking use-cases for
sendBeacon", and it sounds like the simple answer is "yes". Still not
clear how common they will be relative to the tracking use cases in
practice, though. What we do in terms of UI and exposi
The question was simply "are there non-tracking use-cases for sendBeacon",
and it sounds like the simple answer is "yes". Still not clear how common
they will be relative to the tracking use cases in practice, though. What
we do in terms of UI and exposing the ability to disable it depends on
bette
On 2014-04-16, 12:14 PM, Anne van Kesteren wrote:
On Wed, Apr 16, 2014 at 2:30 PM, Richard Barnes wrote:
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/
On 2014-04-16, 2:25 PM, Benjamin Smedberg wrote:
On 4/16/2014 2:18 PM, Richard Barnes wrote:
I don't know about "problematic", but ISTM that it might be useless.
If people disable sendBeacon in an effort to avoid tracking, then the
trackers can always just test and polyfill with XHR. If you re
Are there any legitimate use-cases for, say, saving document drafts before
navigating? It seems pretty bad to make that silently fail.
On Wed, Apr 16, 2014 at 11:25 AM, Benjamin Smedberg
wrote:
> On 4/16/2014 2:18 PM, Richard Barnes wrote:
>
>>
>> I don't know about "problematic", but ISTM that
On 4/16/2014 2:18 PM, Richard Barnes wrote:
I don't know about "problematic", but ISTM that it might be useless. If people disable
sendBeacon in an effort to avoid tracking, then the trackers can always just test and polyfill with
XHR. If you really want "disable tracking", you're going to h
On Apr 16, 2014, at 1:49 PM, Gavin Sharp wrote:
> On Wed, Apr 16, 2014 at 8:56 AM, Ehsan Akhgari
> wrote:
>>> Are beacons primarily meant as tracking devices, or is it also meant as
>>> a way to persist unsaved page state when the user navigates?
>
>> Beacons do not enable any new ways of tra
On Wed, Apr 16, 2014 at 8:56 AM, Ehsan Akhgari wrote:
>> Are beacons primarily meant as tracking devices, or is it also meant as
>> a way to persist unsaved page state when the user navigates?
> Beacons do not enable any new ways of tracking which is not already
> possible.
That's not an answer
On Wed, Apr 16, 2014 at 2:30 PM, Richard Barnes wrote:
> 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
I think that is mostly because
On 2014-04-16, 10:52 AM, Benjamin Smedberg wrote:
On 4/16/2014 9:30 AM, Richard Barnes wrote:
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
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
On Apr 16, 2014, at 10:52 AM, Benjamin Smedberg wrote:
> On 4/16/2014 9:30 AM, Richard Barnes wrote:
>>
>> 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. Howe
On 4/16/2014 9:30 AM, Richard Barnes wrote:
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, removin
14 matches
Mail list logo
