Fragment directives are instructions for user agents to perform some action. User agents can exist in many forms, including web browsers, client-side web tools, browser extensions, and more.
Recently, browsers have started to adopt the URL Fragment Text Directives aka scroll-to-text specification. This introduced undefined and potentially unwanted behavior in regard to how fragment directives should be hidden from and exposed to user agents. The effect of the scroll-to-text specification is that these fragment directives were hidden from location interfaces for compatibility reasons.
This specification 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.
Introduction
Fragment directives are instructions for user agents to perform some action. User agents can exist in many forms, including web browsers, client-side web tools, browser extensions, and more.
Recently, browsers have started to adopt the URL Fragment Text Directives aka scroll-to-text specification. This introduced undefined and potentially unwanted behavior in regard to how fragment directives should be hidden from and exposed to user agents. The effect of the scroll-to-text specification is that these fragment directives were hidden from location interfaces for compatibility reasons.
This specification 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.
Read the complete Explainer.
Feedback
I welcome feedback in this thread, and encourage you to file bugs against the Explainer.