|
The web shell never loaded its font. webfont.js stores the bundled TTF as
base64 in window.__orgflowFontB64, but the fetch/XHR shim in index.html only
looked for globalThis.__orgflowFontBlobs, which nothing ever created. Every
font request therefore fell through to the real fetch, the nested
composeResources path does not exist on the deploy server (its FTP forbids
MKD, which is why the font is shipped flat in the first place), and the app
rendered with no font at all.
Visible effect: every date number and every Japanese label came out as tofu
boxes. Confirmed by capturing the running app - document.fonts reported
"loaded n=0", and the calendar grid showed squares where the digits belong.
Fix: decode __orgflowFontB64 into the Blob map the shim expects. The decode
runs once at parse time and again lazily on the first matching request, because
webfont.js is loaded after this script and may not have run yet when the first
font read happens.
Two other things were established while chasing this, and are worth recording
because they look like application bugs but are not:
- The month grid appeared to stop at the 19th. It was not a layout bug: the
browser chrome left only 650px of viewport, and a 7-column month grid needs
roughly 190px per row, so six rows cannot fit. The screenshot tool now runs
the browser in kiosk mode and sizes it to the full screen (1280x1024), and
the grid shows the whole month plus the out-dates.
- The calendar's "today" cell looked like a two-cell red block in one capture.
It is a single cell; the earlier reading was off because the viewport was
small and the cells were being squeezed.
|
