Since <a ping> has been controversial in the past (for arguably bogus reasons, but controversial nontheless), I suggest we keep it off by default until we find it has some mainstream acceptance and/or we discover that more ports want it.

Regards,
Maciej

P.S. We haven't decided yet if we want it on for the ports Apple ships, but it's probable we will turn it on sooner or later.


On Oct 4, 2010, at 6:51 PM, Jeremy Orlow wrote:

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 <japhet@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> (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