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
RFC #186 introduced per-history-entry unique ids to the HistoryLocation.
But currently on app boot, a new uuid is always generated. This means that when refreshing the page, the same history entry is given a new uuid.
Instead I think we should check history.state for existing state information, and use that if it's available. This would allow an addon to restore things such as scroll position, in line with the motivation of the original RFC.
I believe this would be a fairly straightforward change here, which I'd be happy to work on if no one sees any issues.
The text was updated successfully, but these errors were encountered:
RFC #186 introduced per-history-entry unique ids to the HistoryLocation.
But currently on app boot, a new uuid is always generated. This means that when refreshing the page, the same history entry is given a new uuid.
Instead I think we should check
history.state
for existing state information, and use that if it's available. This would allow an addon to restore things such as scroll position, in line with the motivation of the original RFC.I believe this would be a fairly straightforward change here, which I'd be happy to work on if no one sees any issues.
The text was updated successfully, but these errors were encountered: