Confirmed: BurningTreeC has already signed the Contributor License Agreement (see contributing.md)

This now works and deferres the changes for both styleRefresh and mainRefresh in both the main window and new windows

@Jermolene @pmario @saqimtiaz here's a build with performance instrumentation enabled:

https://rework-throttled-refresh.tiddlyhost.com/

... here's a build with performance instrumentation enabled:

Seems to be slightly faster than the tiddlywiki/prerelease

Actually I wonder why opening $:/TagManager and $:/Manager is especially slow when there are many tiddlers or tags.

Hello @Leilei332 - do you notice this in general or in this PR?

Thanks @BurningTreeC this is promising, but I don't think we're ready to include it in v5.3.6.

One issue is that the code of render.js is now pretty gnarly and hard to follow. I think we need to consider refactoring the rendering and refreshing into a generic class that can be used both for styles and body content. In a separate branch I've been exploring the idea with a new "wikifier" class. See this commit. It will need to be extended to allow it to replace all the occurrences of rendering/refreshing in the system.

✅ Deploy Preview for tiddlywiki-previews ready!

Name	Link
🔨 Latest commit	b8868c8
🔍 Latest deploy log	https://app.netlify.com/projects/tiddlywiki-previews/deploys/6896dbcc46aa0e0009ba7632
😎 Deploy Preview	https://deploy-preview-8677--tiddlywiki-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

📊 Build Size Comparison: empty.html

Diff: ⬆️ Increase: +5.0 KB

I think we need to consider refactoring the rendering and refreshing into a generic class that can be used both for styles and body content.

Hi @Jermolene , I believe I did just that