9 Коммитов

Автор	SHA1	Сообщение	Дата
Sylvestre Ledru	265e672179	Bug 1511181 - Reformat everything to the Google coding style r=ehsan a=clang-format ... # ignore-this-changeset --HG-- extra : amend_source : 4d301d3b0b8711c4692392aa76088ba7fd7d1022	2018-11-30 11:46:48 +01:00
Andrea Marchesini	2035842eaa	Bug 1445587 - Port Fetch to WorkerRef - part 3 - FetchStreamReader, r=smaug	2018-03-16 16:52:29 +01:00
Andrea Marchesini	063723a1f0	Bug 1432963 - Fixing workers headers - part 13 - WorkerHolder without workers namespace, r=smaug	2018-01-31 08:23:44 +01:00
Andrew Sutherland	8244fa6b69	Bug 1416879 - Part 5: FetchStreamReader needs to cancel its reader when it encounters write errors. r=baku, f=bkelly ... Currently, FetchStreamReader never signals to the JS stream code that the reader has been closed. This means that when a ServiceWorker passes a ReadableStream to respondWith and the HTTP Channel gets canceled, the JS code will keep generating the stream without ever realizing the data's not going anywhere. It's necessary to cancel the reader. Or do something like that, this seems to work! --HG-- extra : rebase_source : 88952a917c48b9fa7e421f640b7fb57b15cf7d4d extra : source : 994dc643a2ab62f03fef780a58971b476a4b6f4a	2018-01-04 18:09:32 -05:00
Brindusan Cristian	f42618c99d	Backed out 6 changesets (bug 1416879) for bc permafailures on windows on browser_multie10s_update.js r=backout a=backout ... Backed out changeset 840a6e04bcea (bug 1416879) Backed out changeset 994dc643a2ab (bug 1416879) Backed out changeset 8e4fd74e7f5e (bug 1416879) Backed out changeset 5453b8a58f0c (bug 1416879) Backed out changeset d156f6b687e1 (bug 1416879) Backed out changeset 714d3942fb10 (bug 1416879)	2018-01-07 11:55:44 +02:00
Andrew Sutherland	31246a1058	Bug 1416879 - Part 5: FetchStreamReader needs to cancel its reader when it encounters write errors. r=baku, f=bkelly ... Currently, FetchStreamReader never signals to the JS stream code that the reader has been closed. This means that when a ServiceWorker passes a ReadableStream to respondWith and the HTTP Channel gets canceled, the JS code will keep generating the stream without ever realizing the data's not going anywhere. It's necessary to cancel the reader. Or do something like that, this seems to work! --HG-- extra : rebase_source : 559af90ba766ebd4deb5d99b6696cd2207215f9f	2018-01-04 18:09:32 -05:00
Ben Kelly	8b54ffc436	Bug 1128959 - Implement the WHATWG Streams spec - part 18 - cycle collect FetchStreamReader r=bz	2017-08-10 18:04:56 -07:00
Andrea Marchesini	6e330b0360	Bug 1128959 - Implement the WHATWG Streams spec - part 16 - report stream errors during consumption r=bkelly	2017-08-10 18:04:56 -07:00
Andrea Marchesini	e44cd2d765	Bug 1128959 - Implement the WHATWG Streams spec - part 9 - FetchStreamReader, r=bkelly	2017-08-10 18:04:55 -07:00