Handle Base64 in uris #67

Activity

1. thomlucc

   added this to the 7.0 milestone on Dec 4, 2023
2. thomlucc

   modified the milestones: 7.0, Future on Mar 26, 2024
3. bkaradzic-microsoft commented on Aug 18, 2026

   

   bkaradzic-microsoft

   on Aug 18, 2026

   Member

   More actions

   Being addressed by #212 (open) — Support data URLs in the fetch polyfill, which resolves both percent-encoded and Base64 data: URLs generically (WHATWG forgiving-base64 validation, default/explicit media types, fragment stripping, case-insensitive base64, missing padding, invalid-alphabet rejection), with cases ported from WPT fetch/data-urls and Chromium's DataURL tests — rather than the one-off decode this issue was filed against (BabylonJS/BabylonNative#1328).

   Note on scope: #212 implements data: inside Polyfills/Fetch/Source/Fetch.cpp, so it covers the fetch path only. XMLHttpRequest and other UrlRequest consumers (image/video src, texture loaders) still won't resolve data:. The fully generic answer is the same shape as the blob: work in #207/#213 — a data: scheme resolver registered through UrlLib::UrlRequest::RegisterSchemeResolver, so every consumer gets it uniformly.

   Leaving this open until that generic path exists; #212 is the first (and largest) piece.
4. matthargett

   added 2 commits that reference this issue on Sep 13, 2026

   Resolve data: URLs for every UrlLib consumer via a registered scheme …

   ...

   f30a41c

   Resolve data: URLs for every UrlLib consumer via a registered scheme …

   ...

   418efe6