On 16/5/14 10:29, Tim Taubert wrote:
*Link to Standard*
http://www.whatwg.org/specs/web-apps/current-work/#hyperlink-auditing

A couple of quotes from there:

"User agents should allow the user to adjust this behavior, for example in conjunction with a setting that disables the sending of HTTP Referer (sic) headers. Based on the user's preferences, UAs may either ignore the ping attribute altogether, or selectively ignore URLs in the list (e.g. ignoring any third-party URLs)."

"When the ping attribute is present, user agents should clearly indicate to the user that following the hyperlink will also cause secondary requests to be sent in the background, possibly including listing the actual target URLs."

What's our story here? It's not obvious to me from a (brief) look at the bugs whether we have addressed these issues. Without them, I find the idea of <a ping> quite disturbing...

JK

*Summary*
Anchor tags can have a "ping" attribute that sends asynchronous pings
after or while navigating to the target page for auditing purposes.

*Motivation*
Since bug 786347 landed our Hyperlink Auditing implementation follows
the spec but is disabled by default. If a website wants to audit
navigation to outgoing links (think Google, DuckDuckGo, Facebook, etc.)
it nowadays has to either link to an internal page to record and then
redirect to the target page or use sync XHRs. <a ping> allows to
asynchronously (and with low prio) send one or multiple pings after or
while we start loading the target page.

*Bug to enable by default*
https://bugzilla.mozilla.org/show_bug.cgi?id=951104

*Notes*
The navigator.sendBeacon() API is a superset of <a ping>. <a ping>
allows for lightweight navigation pings without having to use JavaScript.

The number of pings per link is currently limited to 1
(browser.send_pings.max_per_link). Chrome does not limit the number of
pings, we should look into raising or disabling the limit.


- Tim



_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to