Martin Splitt

Would you be interested in moving that forward? We're happy to help, but we don't have ARKit devices available :)

In general, as we're deprecating the project, you should look into alternative approaches to [rendering on the web](https://web.dev/rendering-on-the-web/).

In general, as we're deprecating the project, you should look into alternative approaches to [rendering on the web](https://web.dev/rendering-on-the-web/).

I was just looking into this and it seems to be undocumented behaviour with service workers. This only happens when request interception is enabled. I assume that request interception causes...

In general, as we're deprecating the project, you should look into alternative approaches to [rendering on the web](https://web.dev/rendering-on-the-web/).

In general, as we're deprecating the project, you should look into alternative approaches to [rendering on the web](https://web.dev/rendering-on-the-web/).

Would you have a URL where we can try this out. Also, sounds like this would be a good first pull request, if you want to contribute a solution :)

By disabling the check for HTTP(S) URLs and requesting to serialize "chrome://crash" I am able to reliably reproduce the issue. Thanks for reporting, @imShara

I just updated the demo instance, thanks for pointing this out. The problem I am running into with the automated deployment is that I can't set up a service account...

It's likely to be similar to #484 the root cause being compatibility issues with Shadow DOM v1