-
Notifications
You must be signed in to change notification settings - Fork 548
Add text for the ping attribute #369
Comments
Given what I'm hearing about the privacy group potentially having concerns over adding this API into 5.1, and given our relatively short timeline, I think we are OK with moving this issue to 5.2 and adding it to the spec in order to have time for wider review and resolution of potential issues as a result. |
As well as |
(Live notes from discussion with the Privacy Interest Group) Note that if we have a requirement that user agents clarify to the user that the link will ping other sites, we need to test whether that happens in real implementations. Note also that among privacy considerations, this can improve the ability to offer privacy because it's declarative and easily parsed, meaning user agents could inform users and allow them to control what happens more effectively than where javascript is used for this kind of tracking |
Based on data from caniuse.com: Chrome/Opera and Safari support the ping attribute, Firefox has support behind the browser.send_pings flag, but it's disabled by default), and neither Edge nor IE support it at all. Should we reintroduce the ping attribute into the HTML5.3 spec? |
@travisleithead thoughts on this for edge? |
I think Edge is amenable to implementing this in the near future, if that helps 😊 |
Based on all the comments above, I think we should go ahead with it then. |
Previous there was a CfC, which passed, to remove PING from HTML 5. Part of the rationale for the original change proposal was that, "The feature is half-baked, insufficiently implemented, and therefore not yet suitable for standardization."
There are now multiple implementations of the ping attribute and this decision should be revisited with this new information.
The resolution of the CfC said, "The feature could still be proposed again for a later issue of HTML, or the issue could be re-raised if new information is provided (such as implementation experience or server-side deployment experience.)"
The text was updated successfully, but these errors were encountered: