Using viewTransition: true breaks application in WKWebView

[boliveira]

Hi everyone,

I am getting a strange behavior when running my app using React Router's viewTransition when navigating to new routes. If I run it inside a WKWebView, sometimes after navigating to a route, the DOM is updated but the UI is of the previous page. It seems to be a composition problem as if I force changing the opacity of the root element to like 0.99, the UI is updated to match the DOM.
When running inside Safari Mobile it does not happen.
Does anybody know of any problem with WKWebView with the View Transition API?

[aaronbutler1515-cyber]

It sounds like you're hitting a WebKit compositing bug rather than an issue in React Router itself. viewTransition relies on the browser correctly updating layer composition after the DOM changes. In WKWebView, there are known cases where the DOM updates but the rendered layer tree does not refresh immediately, especially when View Transitions, transforms, fixed-position elements, or accelerated layers are involved.

…

On Thu, Apr 2, 2026, 1:08 PM Bruno Oliveira ***@***.***> wrote: Hi everyone, I am getting a strange behavior when running my app using React Router's viewTransition when navigating to new routes. If I run it inside a WKWebView, sometimes after navigating to a route, the DOM is updated but the UI is of the previous page. It seems to be a composition problem as if I force changing the opacity of the root element to like 0.99, the UI is updated to match the DOM. When running inside Safari Mobile it does not happen. Does anybody know of any problem with WKWebView with the View Transition API? — Reply to this email directly, view it on GitHub <#11231?email_source=notifications&email_token=B72ORAUIRZQNQBTHZ4FVDD34T2UAXA5CNFSNUABAM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPHE4DCNBXGU4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B72ORASUGPQYKNPGXU2SAEL4T2UAXAVCNFSM6AAAAACXK4WIC2VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZHAYTINZVHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>