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

Spec should mention risk of "hl" colliding with an existing query or fragment parameter #11

Open
kimdhamilton opened this issue Apr 29, 2020 · 1 comment

Comments

@kimdhamilton
Copy link
Contributor

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.

@BigBlueHat
Copy link

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. 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants