[Streams API] Finish pulling must always be done asynchronously as it is the expected...
authorcalvaris@igalia.com <calvaris@igalia.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 30 Jun 2015 09:53:40 +0000 (09:53 +0000)
committercalvaris@igalia.com <calvaris@igalia.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 30 Jun 2015 09:53:40 +0000 (09:53 +0000)
commitc5c42e6100703b71ff82303434590a518d42d394
treeb48990cb300c2e090f2d8f8bb400adc41b1f6601
parent6a80252dd80aa941ff55a215b90b24e5aa2c1c65
[Streams API] Finish pulling must always be done asynchronously as it is the expected promise behavior (according to the spec)
https://bugs.webkit.org/show_bug.cgi?id=146408

Reviewed by Darin Adler.

Source/WebCore:

Current tests cover the case already.

* Modules/streams/ReadableStream.cpp:
(WebCore::ReadableStream::pull): Call finishPull() in a postTask to delay it and simulate the promise
resolution.

LayoutTests:

* streams/reference-implementation/readable-stream-expected.txt: Updated expectation to PASS

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@186113 268f45cc-cd09-0410-ab3c-d52691b4dbfc
LayoutTests/ChangeLog
LayoutTests/streams/reference-implementation/readable-stream-expected.txt
Source/WebCore/ChangeLog
Source/WebCore/Modules/streams/ReadableStream.cpp