Fragment Directives API

[eligrey]

I am proposing a specification for adoption by the PrivacyCG that aims to codify a way to read and write fragment directives from all supported location interfaces while accounting for the privacy concerns introduced by accessing potentially privacy-sensitive directives (e.g. text).

My proposed spec: https://github.com/eligrey/fragment-directives

Related issue in scroll-to-text spec repository: WICG/scroll-to-text-fragment#128

[eligrey]

@zcorpan left some feedback here about permission prompts and determining what directives should be considered sensitive: eligrey/fragment-directives#1

[eligrey]

I intentionally chose to re-use URLSearchParams in this spec for implementation simplicity, but I can introduce URLFragmentDirectives if there is interest for it. If we re-use URLSearchParams there will be a slight API ergonomics concern with the leading ? in string representation. That could be easily special-cased to be ignored.

Aside from the obvious string representation difference, a URLFragmentDirectives constructor could also parse out fragment directives from a full hash fragment.

[eligrey]

Full disclosure: I work for Transcend, and we currently use performance.getEntries() as part of our implementation of accessing custom fragment directives for our consent manager SDK. We use the compat behavior to help ensure that our URL-based configuration options won't interfere with routing on customer sites.

[martinthomson]

@eligrey can you explain why you think Privacy CG is the right forum to develop this proposal? From what I can see, this is a straightforward extension to the text fragment work that is being developed in WICG. I would suggest that you seek to engage in that forum, probably with the proponents of that work.

@jyasskin you asked for time on our agenda for this. Can you give me a little more context? If we are going to set aside time, then we'd need to know who would be leading that work and what you would hope to achieve. Is it simply a request to discuss adoption as Eli requests?

[jyasskin]

Eli asked someone to agenda+ it in https://w3cping.slack.com/archives/CSVA13FJB/p1696271146530939, so I did.

[erik-anderson]

This was discussed on our October 12th call: https://github.com/privacycg/meetings/blob/main/2023/telcons/10-12-minutes.md. While it wasn't captured in the minutes, I think something along the lines of Martin's feedback about taking this proposal to the WICG was given.

@eligrey any objections to closing out this issue here? Feel free to add a pointer to the new location.

[eligrey]

Yeah, I'm fine with closing this out. I'll post a new link here once I've moved the proposal over to WICG.

[eligrey]

This has been re-proposed under WICG: WICG/proposals#154