Why does my liveview app resort to longpoll on chrome, websocket on firefox?

anuvrat · April 30, 2024, 11:15am

I notice that my liveview app resorts to longpoll when accessed via chrome browser.
But on firefox, websockets work fine.

Am I missing some configuration?

BartOtten · April 30, 2024, 7:42pm

LiveView sets a key in session storage when it resorts to longpoll and uses longpoll when that key is set. This might happen due to a (dev) server restart when the connection is lost for a brief time.

That might be the issue. Clear the session storage for the domain and see if it solves the issue.

github.com/phoenixframework/phoenix

Longpoll fallback is preserved after server restart and browser reload

opened 04:26PM - 04 Mar 24 UTC

closed 06:06PM - 11 Mar 24 UTC

clarkware

### Environment * Elixir version (elixir -v): 1.16.1 * Phoenix version (mix …deps): 1.7.11 * Operating system: macOS Sonoma 14.3.1 ### Actual behavior In development, when the browser is on a LiveView page and the server is restarted, the longpoll fallback kicks in. However, reloading the browser page doesn't attempt to reconnect a websocket since the `phx:longpoll` key is set to `true` in `sessionStorage`. ### Expected behavior I'm not sure if the behavior above is expected or not. I found it confusing during development since you often restart the server for one reason or another, and expect things to continue working over websockets.