fix(web): give the browser build a load_file to fail through

Reading a drawing by path is gated off on wasm, and two features added
since 0.9.3 call it unconditionally: importing a drawing as a block, and
taking layer standards from one. Both compile into the web build, so the
web bundle stopped building and the v0.9.4 Pages deploy failed.

Neither feature can work in the browser — a file arrives through the page,
not from a filesystem the app can open — so the fix is not to make them
work but to let them say so. `load_file` now exists on wasm and returns
that as its error, which both callers already surface. Keeping the
signature means neither has to know that the web has no files, and the
next feature that reads a second drawing will not break the bundle
either.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Hakan Seven 2026-08-08 03:34:57 +03:00
commit 6ca4463a26
3 changed files with 15 additions and 0 deletions

View file

@ -3436,3 +3436,4 @@ catalog-tcount-placement-must-be-overwrite-prefix-or-s-84211d2b75 = TCOUNT: plac
catalog-tcount-numbered-n-text-object-s-from-start-by-30588884cc = TCOUNT: numbered __ocs_fmt_0__ text object(s) from __ocs_fmt_1__ by __ocs_fmt_2__ (__ocs_fmt_3__).
catalog-prefix-90eceb016c = Prefix
catalog-suffix-885db975a3 = Suffix
catalog-opening-a-drawing-by-path-is-not-available-in-be27bd71d4 = Opening a drawing by path is not available in the browser.