XHR: separate delayed progress event flushing from dispatching of new.
The throttled delivery of progress events may defer progress event
delivery so as to pace their dispatching down to the frequency that
the spec suggests. When dispatching a later 'readystatechange' event,
if no deferred progress event was present, a new one would be created
and dispatched. Achieving the same event sequence despite the
lazy/deferred delivery of 'progress' events.
There are two steps involved here: the potential expedition of the
deferred progress event and the creation & delivery of a new one.
Tease these two notions apart here by allowing only flushing of
a deferred progress event to happen.
This weaker form of flushing is needed by follow-on changes, which
alters how these 'progress' progress events are dispatched wrt the
'readystatechange' XHR event when handling request errors and aborts.
R=
BUG=315488
Review URL: https://codereview.chromium.org/62193004
git-svn-id: svn://svn.chromium.org/blink/trunk@162270 bbb929c8-8fbe-4397-9dbb-9b2b20218538
2 files changed
