You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per discussion on the mailing list, the spec should mention that one of the drawbacks of using a hashlink as a query parameter or a fragment identifier is the risk of "hl" colliding with an existing parameter.
The text was updated successfully, but these errors were encountered:
Browsers (at least) now support "fragment directives"--see the following from MDN on text fragments:
:~:
Otherwise known as the fragment directive, this sequence of characters tells the browser that what comes next is one or more user-agent instructions, which are stripped from the URL during loading so that author scripts cannot directly interact with them. User-agent instructions are also called directives.
Perhaps that approach could be explored instead--as this would be a "user-agent instruction" by definition...even if the user-agent is curl and bash. 😃
Per discussion on the mailing list, the spec should mention that one of the drawbacks of using a hashlink as a query parameter or a fragment identifier is the risk of "hl" colliding with an existing parameter.
The text was updated successfully, but these errors were encountered: