Given that a ping really doesn't open up any new privacy holes (just makes
it easier for sites to get the data they're going to gather anyway without
slowing down the experience for the user), it seems like we might as well
enable it by default.  If a port doesn't want it, they can always disable
it, right?

Thanks,
J

On Fri, Oct 1, 2010 at 12:39 PM, Nate Chapin <jap...@chromium.org> wrote:

> This is a few days late, but I just wanted to let the team know that, as of
> http://trac.webkit.org/changeset/68166, WebKit can support <a 
> ping><http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#hyperlink-auditing>(but
>  support is disabled by default).
>
> The reason I left it disabled by default is that some ports may want to
> have a mechanism for disabling pings, and I didn't want anyone
> to accidentally pick it up before they were ready.  I'm happy to flip it to
> enabled by default if that's what people prefer.
>
> ~Nate
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Reply via email to