[Webkit-unassigned] [Bug 245350] Websocket disconnects in Safari when user switches out to another app when experimental feature "NSURLSession WebSocket" is turned on

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=245350

--- Comment #12 from chris.ng.hs.code at gmail.com ---
(In reply to chris.ng.hs.code from comment #11)
> Hey Alexey, 
> 
> In a summarized use case:
> 1) In Safari web socket is connected
> 2) User gets directed to another mobile application to trigger an event in
> websocket, event message triggered on mobile application *this event will
> only get triggered once
> 3) user gets back to Safari, websocket is disconnected, event that is
> triggered in point 2. is already lost. Reconnecting to the websocket room
> will not have any effect as point 2 has already happened

And yep, if its disconnection due to network issues, we can prompt the user to trigger a reconnection, and perform the above flow again. But that only works for the us based on the above flow if the websocket remains connected to receive the message in point 2, else the issue persists.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220927/f2b53f98/attachment.htm>