[Webkit-unassigned] [Bug 30458] New: Implement <a ping>
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Oct 16 14:13:54 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30458
Summary: Implement <a ping>
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: jam at chromium.org
Creating a bug from the webkit-dev discussion. It seems there's consensus on
doing this. The main reasons are that without a robust way to handle tracking,
ad networks and other sites are resorting to redirects and busy loops in unload
handlers after image loads. This hurts the user since it slows down their
navigation and consumes battery on mobile/laptop devices. Adding ping doesn't
reduce the privacy, since it's something that's already done using hacks. This
should improve privacy since user agents can then expose options to the user to
disable this feature, just like for referral headers.
This is part of HTML5:
http://www.whatwg.org/specs/web-apps/current-work/#hyperlink-auditing
Note: once we do this, there are a few people who think we should implement
window.sendPing() as well. The reasons are that <a ping> won't work for
iframes, which is how it's used by ad networks.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list