This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently webapps cannot control when a flush/sync should be performed after writes, so that it's not really clear what data would be read right after writes. The UA cannot make a good decision about when to flush/sync either. The API should provide a way for webapps to make sure the data they've written are actually written to a persistent storage.
Work on this specification has stopped.