Re: [w3ctag/design-reviews] App history API (#605)

Thanks to you both for the kind words! I do understand this is a pretty large explainer, and I apologize for that. We did recently add a summary section and early code examples that might help a bit. Please take all the time you need.

BTW, I realized that

> There are a number of minor TODOs scattered throughout the document and issue tracker; thoughts on the best ways of resolving those would be appreciated.

is less than helpful, especially since there's a mix of "TODO fill in this example", "TODO figure out this minor API issue", and "TODO bigger architectural issue". I've pulled out the ones where thoughts would be especially appreciated into the following issues, sorted roughly in order of most-architectural to least-architectural:

- Should we allow more direct control over when the URL bar updates? https://github.com/WICG/app-history/issues/66
- What design should be used for reporting navigation duration? https://github.com/WICG/app-history/issues/33
- Should this API be able to completely replace `window.history` and `window.location`? https://github.com/WICG/app-history/issues/67
- Should app history events be fired on page load? https://github.com/WICG/app-history/issues/31


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/605#issuecomment-794606658