We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current API proposal for uistate hash portion serializes as a string, and the API makes it easy to accidentally overwrite an existing value.
A better API would provide scoping so that other pieces of the page could update the hash without knowing about existing uistate.
The text was updated successfully, but these errors were encountered:
Agreed. In this case it'd be a requirement since, unlike :~:text=, it's more likely to have :~:uistate= and fragment at the same time.
:~:text=
:~:uistate=
Sorry, something went wrong.
No branches or pull requests
The current API proposal for uistate hash portion serializes as a string, and the API makes it easy to accidentally overwrite an existing value.
A better API would provide scoping so that other pieces of the page could update the hash without knowing about existing uistate.
The text was updated successfully, but these errors were encountered: