This isn't a limitation in chrome itself, which means chrome rendering has better performance for these specific operations (animations mostly).
Personally I think the chrome rendering path should always be used, and apps which want to draw under/over web content will have to deal with a frame or two of delay.
Unfortunately, companies have an incentive to put us into walled gardens, so the only company that actually cares about the web is the company whose only business model is selling a browser.
Basically, FB's engineering replaced it with a full chromium based webview and explained the reasons android webview sucks ass.
There's Tauri, which does use a dynamic loading approach. But the various browsers it uses are nowhere near as capable and featureful as chrome, which is so sad. I don't know when it got started but there is https://github.com/tauri-apps/cef-rs now, using Chromium Embedded Framework, which is pleasantly modern & can share a binary too; rad.
About a decade ago iOS only had UIWebView which was significantly worse than Safari. This affected all apps using a webview including competing browsers.
