Re: [w3c/FileAPI] TPAC 2026 Status Report (Issue #224)

mkruisselbrink left a comment (w3c/FileAPI#224)

**1. Progress in the last 12 months**

Since TPAC 2025 a handful of fixes/additions were merged:

- `Blob.textStream()` ([#221](https://github.com/w3c/FileAPI/pull/221), Jun 2026)
- Fix for top-level self-fetch of `blob:` URLs ([#216](https://github.com/w3c/FileAPI/pull/216), Dec 2025)
- MIME type/encoding cleanups ([#223](https://github.com/w3c/FileAPI/pull/223))
- Environment-based access checks for blob URLs ([#225](https://github.com/w3c/FileAPI/pull/225), Sep 2026)

Separately, @jcayzac has a draft PR to fold the File and Directory Entries API into File API ([#222](https://github.com/w3c/FileAPI/pull/222), see also [WICG/entries-api#48](https://github.com/WICG/entries-api/issues/48)). The direction agreed with @annevk is to standardize the prefixed (`webkit*`) names as they are implemented today, and possibly add unprefixed versions later. There is also some outside interest from EPUB in reusing these concepts for a ZIP file system ([w3c/epub-specs#3083](https://github.com/w3c/epub-specs/issues/3083)).

**2. Blockers**

The main blocker is editor time. The read/stream algorithms are still underdefined in a number of places ([#208](https://github.com/w3c/FileAPI/issues/208), [#206](https://github.com/w3c/FileAPI/issues/206), [#199](https://github.com/w3c/FileAPI/issues/199)), and the security/privacy self-review ([#214](https://github.com/w3c/FileAPI/issues/214)) is still open.

For the Entries API merge, someone still needs to land the corresponding changes in WHATWG HTML. That probably needs to be someone with WHATWG involvement (I can probably take that on), and @jcayzac would need editor access on this repo.

**3. Testing plan**

The core APIs have good coverage in WPT, and the `textStream()` tests landed in [wpt#60356](https://github.com/web-platform-tests/wpt/pull/60356). Most remaining work is spec text catching up with what WPT and implementations already do (e.g. [#226](https://github.com/w3c/FileAPI/issues/226), where all engines and WPT already preserve `type` when serializing Blob/File).

**4. Next steps / help needed**

Finish merging the entries API work, and make progress towards getting this spec to CR.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/224#issuecomment-6352357732
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/issues/224/6352357732@github.com>