Request for feedback on new browser API proposal ("app history")

[domenic]

Hi ReactTraining/history maintainers and community members,

The Chrome team has been exploring various issues with the web's history API, and working on a new API proposal to solve them. You can read more at WICG/proposals#20.

Given your extensive experience dealing with the existing browser history API, as well as designing one that is more pleasant to use, we'd love your thoughts on the proposal. For example, perusing your docs I noticed that getting a signal as to what type of navigation was happening (push/pop/replace) is important; I want to add that to the proposal, since it's not currently there. Additionally, if there are things we could add to the API to make your library more capable or work better, that would be great information.

Thanks for your time!
-Domenic