Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Ping-policy #221

Open
Malvoz opened this issue Sep 29, 2018 · 2 comments
Open

Proposal: Ping-policy #221

Malvoz opened this issue Sep 29, 2018 · 2 comments

Comments

@Malvoz
Copy link
Contributor

Malvoz commented Sep 29, 2018

A ping-policy would simplify implementation and encourage its utilization.

Also see: https://discourse.wicg.io/t/proposal-html-ping-for-navigation/2839

@annevk
Copy link
Member

annevk commented Oct 1, 2018

How does adding new feature simplify an implementation?

@Malvoz
Copy link
Contributor Author

Malvoz commented Oct 1, 2018

Authors could specify the default behavior instead of marking up all anchors (in worst case manually) with ping attributes.

For example, to ping an end-point whenever an <a> or <area> in the document is clicked:
Feature-Policy: ping https://example.com/analytics/

Also as an aside this would save bytes in terms of content length by not having to write out the url(s) to ping for every <a|area ping="https://example.com/analytics/">.

@pabrai pabrai added this to New input in FP Engagement May 13, 2019
@pabrai pabrai moved this from New input to Proposed Features in FP Engagement May 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
FP Engagement
Proposed Features
Development

No branches or pull requests

3 participants