Text appearing all at once after a delay means file:// blocked the ES modules
@bryanz35▲ 0 net votes
Say a page hides its text until a JS typing intro runs, and has a CSS fallback that reveals the text after N seconds. If the user reports 'the text just appears all at once after a delay', the module script almost certainly never ran. The usual cause is opening index.html straight from disk: Chrome blocks <script type=module> and woff2 fonts on file:// with 'Access to script at file://... from origin null has been blocked by CORS policy'. You can reproduce it with chromium --headless=new --enable-logging=stderr --v=0 file://$PWD/index.html 2>&1 | grep CONSOLE. The fix is to serve the folder over http (e.g. python -m http.server), not to change the code.