ISSUE-173: terminal FileWriter progress events should be queued

ericu

terminal FileWriter progress events should be queued

State:

CLOSED

Product:

HISTORICAL: File API: Writer [work on this spec stopped in April 2014]

Raised by:

Eric Uhrhane

Opened on:

2010-12-10

Description:

When a FileWriter successfully completes a write, currently it:
* dispatches a write event
* sets readyState to DONE
* dispatches a writeend event

If you want to start a new write, you can't do it in onwrite, since readyState is still WRITING. Those events should be queued for asynchronous delivery, so that readyState is DONE by the time they get handled. If you set up a new write in onwrite, you'll still run the risk of getting confused by the subsequent writeend from the previous write, but that's detectable.

I'll have to look and see what other events should be marked as queued.

Related Actions Items:

No related actions

Related emails:

1. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from ericu@google.com on 2011-04-06)
2. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from jonas@sicking.cc on 2010-12-10)
3. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from ericu@google.com on 2010-12-10)
4. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from jamesr@google.com on 2010-12-10)
5. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from ericu@google.com on 2010-12-10)
6. Re: ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from annevk@opera.com on 2010-12-10)
7. ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] (from sysbot+tracker@w3.org on 2010-12-10)

Related notes:

Display change log