fix: implement ASYNCIFY-based async font loading in GTK widget factory demo #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes runtime crash caused by fonts loading asynchronously after FcInit() call.
ROOT CAUSE:
SOLUTION:
Implement ASYNCIFY-based polling for font availability before initializing fontconfig/Pango. This allows C code to "sleep" and yield to the JS event loop while fonts are being loaded.
CHANGES:
main.c:
build-final.sh (NEW):
test-wasm-init.ts:
EXPECTED BEHAVIOR:
✅ Fonts load before FcInit() call
✅ FcInit() finds ≥4 fonts (Regular, Bold, Italic, BoldItalic) ✅ Pango initializes without NULL pointer crash
✅ Font rendering works in widget factory demo
Console output:
[WASM] Widget factory demo starting...
[WASM] Waiting for fonts to load...
[WASM] ✅ Fonts available after 0ms
[WASM] Initializing fontconfig...
[WASM] Found 4 fonts:
[WASM] Roboto Regular
[WASM] Roboto Bold
[WASM] Roboto Italic
[WASM] Roboto BoldItalic
[WASM] ✅ Fontconfig initialized with embedded fonts
ASYNCIFY OVERHEAD:
BUILD:
cd demos/webgpu-widget-factory
bash build-final.sh
TEST:
deno test --allow-read --allow-write --import-map=import_map.json test-wasm-init.ts