Jonathan Perret

> There's a case for doing that, since CI style testing doesn't really capture the diversity of browsers and company firewalls and network latency out there. But I'd guess this...

I have updated the PR description to reflect the current implementation status. I have also pushed a commit that adds `GRIST_USE_ENGINE_IO=1` to the environment in `fly-template.toml`, hopefully this is how...

The Fly deployment failure seems caused by the fact that PRs based on branches from forks do not have access to repository secrets, for obvious security reasons. You may have...

Testing with a more complex deployment including multiple doc workers and a load balancer revealed that the addition of the `/engine.io/` prefix to socket requests meant that some load balancer...

Hi! I added a few commits that : - remove the `/engine.io/` prefix previously added to WebSocket and polling request paths; this should make the new protocol compatible with practically...

Hi @dsagal , I finally found the time to work on this again, putting in what will hopefully be the last big change. For origin verification, I added a `verifyClient`...

Thank you guys for helping bring this to fruition. Can't wait to deploy it and unlock the power of Grist for our restricted-network users. @paulfitz I see what you mean....

Audio mixers have "solo" and "mute" buttons:  The behaviour you're talking about sounds like a special case of a "solo" button to me. Likewise, image editors have the usual...

Can you please open a PR so that we get a review app?

A renderer that does not render anything is arguably not very useful. How about using `about:blank` as an URL for that case?