Skip to content

Make it optional to show UI for <a ping> #11329

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

zcorpan
Copy link
Member

@zcorpan zcorpan commented May 22, 2025

Fixes #11309.

(See WHATWG Working Mode: Changes for more details.)


/infrastructure.html ( diff )
/links.html ( diff )
/system-state.html ( diff )
/web-messaging.html ( diff )
/webappapis.html ( diff )

@npdoty
Copy link

npdoty commented May 22, 2025

If the spec were to no longer recommend user transparency, then you should simultaneously remove the part of the note in this section that recommends that authors use the ping attribute "so that the user agent can make the user experience more transparent". Instead, it would seem like the advantage to authors is that there would be less transparency to the user about how their activity is being tracked and less performance risk in doing that kind of tracking.

For many years this feature was justified as potentially providing privacy benefits, but if those requirements are removed, you could at least remove the pretense.

@zcorpan
Copy link
Member Author

zcorpan commented May 22, 2025

Good point, fixed.

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but let's wait for a bit to get more eyes on this.

Thanks for aligning the spec with reality here.

@domenic domenic added security/privacy There are security or privacy implications topic: hyperlink labels May 23, 2025
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I like tying it to script execution, do we have any indication that it's going to be followed? If we want that to be model we should require it, but it's not entirely clear to me it's worth doing.

@zcorpan
Copy link
Member Author

zcorpan commented May 26, 2025

I'm not aware of plans of it being implemented for ping.

Scripting is disabled check is used by lazy-loading, which is implemented (see wpt). However, CSS can probably be used to "ping" when a link is clicked (with :active) or when something is scrolled into view (with scroll-driven animations).

Either the CSS features need to also be have a scripting-disabled check, or the HTML features should keep working when scripting is disabled, I think.

@zcorpan
Copy link
Member Author

zcorpan commented Jun 5, 2025

I removed the scripting is disabled check.

@domenic
Copy link
Member

domenic commented Jun 5, 2025

I think we've waited long enough; feel free to merge!

@npdoty
Copy link

npdoty commented Jun 6, 2025

Did it seem like we had consensus on #11309? I've tried my best to clarify the potential harm to users and privacy-friendly sites.

@domenic
Copy link
Member

domenic commented Jun 7, 2025

Yes, you've made your position clear; thank you for doing that! That doesn't prevent merging changes.

Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a couple of nits so the paragraph is annotated in the usual way (and then I made that overall annotation more consistent).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security/privacy There are security or privacy implications topic: hyperlink
Development

Successfully merging this pull request may close these issues.

Remove UI requirement for <a ping>
4 participants