This is related to the clientId and indexed db storage mentioned in the current draft of the spec. Will it be recommended for a web page to take advantage of the history.state for pause/resume? In all other respects, the history state storage could be a good ephemeral storage mechanism that naturally gets thrown out when a tab is closed. The History API in its current state is not very convenient for something like this, but otherwise this storage seems to fit well?
This is related to the
clientId
and indexed db storage mentioned in the current draft of the spec. Will it be recommended for a web page to take advantage of thehistory.state
for pause/resume? In all other respects, the history state storage could be a good ephemeral storage mechanism that naturally gets thrown out when a tab is closed. The History API in its current state is not very convenient for something like this, but otherwise this storage seems to fit well?