This is an old behaviour because of the web-client's history of originally using WebSockets exclusively, back when it was the "command channel", and the UI would send requests and receive responses entirely over WS. Since this has been phased out in favour of an HTTP REST-ish API, and WebSockets are only used to push notifications from the server, it no longer makes sense for the web-client to wait for the WebSocket connection to be established before querying for the target list or any other data from the server.
Current Behavior
See #1271
This is an old behaviour because of the web-client's history of originally using WebSockets exclusively, back when it was the "command channel", and the UI would send requests and receive responses entirely over WS. Since this has been phased out in favour of an HTTP REST-ish API, and WebSockets are only used to push notifications from the server, it no longer makes sense for the web-client to wait for the WebSocket connection to be established before querying for the target list or any other data from the server.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response