W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Beacon API

From: イアンフェッティ <ifette@google.com>
Date: Fri, 15 Feb 2013 03:51:56 -0800
Message-ID: <CAF4kx8cWRQwZeYM-L9tKJdRY3JQ9-2RXNJkft9b=Q2dDU-5pvg@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Ilya Grigorik <igrigorik@google.com>, Web Applications Working Group WG <public-webapps@w3.org>
Anne,

Both Chrome and Safari support the ping attribute. I am not sure about IE,
I believe Firefox has it disabled by default. FWIW I wouldn't consider this
a huge failure, if anything I'd expect over time people to use ping where
it's supported and fallback where it's not, resulting in the same privacy
tradeoff for users of all browsers but better performance for some browsers
than others, which will eventually lead to a predictable outcome...

-Ian

On Fri, Feb 15, 2013 at 3:06 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Fri, Feb 15, 2013 at 12:21 AM, Ilya Grigorik <igrigorik@google.com>
> wrote:
> > A lot of the discussion so far focused on the async analytics beacon +
> > unload use case. However, while this is an important case to consider,
> let's
> > not constrain this proposal to "on unload" case only.
>
> Just to be clear. I understand why we'd want this. I'm a) wondering
> why it'll be successful this time given it has the same
> characteristics as ping="" b) asking about the desired timeframe given
> the highly likely introduction of a new Future-based API for fetching.
>
>
> --
> http://annevankesteren.nl/
>
>
Received on Friday, 15 February 2013 11:52:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT