Jonathan Kew wrote: > "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)."
Users can disable sendings pings by flipping a preference. They can limit the number of pings sent per link. They can restrict pings to the same host as the document in which the click occurs by flipping a pref. > "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." This is covered by bug 401352. > 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... We don't have a story here at the moment. Sites currently audit external navigation by using redirects and sync XHRs which don't notify the user either but at the same time make navigation a lot slower. Calling the whole idea of <a ping> "disturbing" makes it sound like we would introduce a whole new concept, we just provide a saner way to do things that lots of web pages want. There is no obvious disadvantage to the user from my POV here. - Tim >> *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 >> >> > -- Tim Taubert Engineering Manager, Firefox @ttaubert _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
