For browser crashes, forced app closures, etc, the browser should make an effort to send the beacons the next time it is launched (guarantees around privacy and reliability here will be the same as the Reporting API’s crash reporting).

Filing this issue to track relevant discussion

1. This is blocked by privacy concern: [Privacy] Address privacy requirement around "network changes" #30
2. Per discussion from TPAC meeting, even without 1, the usage of an outdated pending beacon recovered from, e.g. 24 hours ago, might be pretty limited in terms of analytics.
3. Plus, user can already use local storage to achieve similar things without a new API.