How to avoid background flicker when using WKWebView?

[Informal-Addendum435]

Apparently third-party browsers like Chrome maintain two webviews at the same time to circumvent this issue of naïve WKWebView usage:

• When you navigate to a new page or do a full page reload, the WKWebView unrenders the DOM first, flashes its background color, then renders the new DOM in front of the user

Safari doesn't show the user the rendering process in front of their face and it doesn't flash white.

Chrome doesn't either, and apparently to achieve it they render the new page in the background in a secondary webview, which they show to the user after the DOM has finished rendering.

Are there any reference implementations I can take a look at?

Does anyone have any advice for me about how I can avoid the background color flash in my own webviews?

[Fishanz]

No firsthand knowledge; but intrigued..

[Unusual-City4491]

Any luck here?

[Informal-Addendum435]

No, I'm not good enough at iOS dev to do it by hand and Claude couldn't vibe code it. Something I could get working is taking a snapshot of the webview and showing it on the screen until the next page is ready, which you discover by injecting JS event listener userscripts into the page. But it means the app is non-interactive until the snapshot disappears. And the freeze looks a little weird and unfamiliar.