eezd/RawMark
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

fix: keep the interface visible while fonts load
Development CI / check-and-package (push) Successful in 3m48s
Details
GitHub Git mirror / mirror (push) Successful in 5s
Details
Development CI / image (push) Successful in 20s
Details
Development CI / deploy-development (push) Successful in 15s
Details

Browse Source 
Render fallback fonts immediately and preload regular Maple in the background. Cache public fonts after use without eagerly downloading every font during PWA installation.
This commit is contained in:
eezd committed 2026-10-30 18:28:00 +08:00
1 parent 716b495440
commit 6cbd604a28
16 files changed
+344 -308
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/development.md
+1 -1
View File
@@ -90,7 +90,7 @@ Default font resources are checked in; ordinary builds require no download or co
python3 scripts/prepare-maple-font.py /path/to/MapleMonoNormalNL-NF-CN.zip
```
The script generates WOFF2 files and `maple-font.css` while retaining the upstream license. Code blocks use highlight.js with fixed Atom One Dark; theme changes must not reintroduce previous highlighters or color schemes.
The script generates WOFF2 files and `maple-font.css` while retaining the upstream license; `--css-only` regenerates declarations without rebuilding font binaries. Fonts use swap rendering, so downloads never hide the page. After first paint, regular Maple chunks (about 6.72 MB) load in batches of two; other weights load on demand. PWA installation skips font files and caches public build fonts after use. Code blocks use highlight.js with fixed Atom One Dark; theme changes must not reintroduce previous highlighters or color schemes.
Plugin SDK types are in [common/plugin-api/index.d.ts](../web/src/common/plugin-api/index.d.ts); loading and lifecycle code lives in `common/plugins/`. Plugins run only on the frontend, and installers must trust their code. Namespaces, disabling, and resource versioning do not constitute a permission sandbox. Editor-extension failures preserve document contents and disable the relevant extensions on the current page.