[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 #8 from chris.ng.hs.code at gmail.com ---
Thanks Alex for the reply. Yes, for scenarios where there are no connection we will show the user that they have been disconnected and they will have to retry. But however where there isn’t any connection issues, the websocket should be able to remain connected and receive the information when switched out to other apps, but however for Safari, our users have to turn off the experimental feature to be able to work.

 All the other browsers(edge, chrome, Firefox..) are working fine and able to receive the information without any particular settings needed and they are still able to get the websocket information when user switched out to another app to send trigger the websocket event.

Just wondering if this is still work in progress and to be resolved by the apple developers or it’d be a limitation specifically only for IOS safari 15/16, will help for developers to implement instructions to disable the experimental feature.

-- 
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/9b370dbe/attachment.htm>