uistate hash, similar to history.state, is easy to clear

[tbondwilkinson]

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.

[dvoytenko]

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.