From 5b771e7e83b32402f06873e684efb2381971e0f6 Mon Sep 17 00:00:00 2001 From: Andreu Botella Date: Wed, 14 Jul 2021 12:08:42 +0200 Subject: fix(extensions/web): aborting a FileReader should not affect later reads (#11381) Currently, calling the `abort()` method on a `FileReader` object aborts any current read operation, but it also prevents any read operation started at some later point from starting. The File API instead specifies that calling `abort()` should reset the `FileReader`'s state and result, as well as removing any queued tasks from the current operation that haven't yet run. --- tools/wpt/expectation.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools') diff --git a/tools/wpt/expectation.json b/tools/wpt/expectation.json index 4124efe7c..0fb126066 100644 --- a/tools/wpt/expectation.json +++ b/tools/wpt/expectation.json @@ -2794,7 +2794,7 @@ "reading-data-section": { "Determining-Encoding.any.html": true, "FileReader-event-handler-attributes.any.html": true, - "FileReader-multiple-reads.any.html": false, + "FileReader-multiple-reads.any.html": true, "filereader_abort.any.html": true, "filereader_error.any.html": true, "filereader_events.any.html": false, -- cgit v1.2.3