You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
fd6e2954f7
Closes #173 Previously, in the event of a failed websocket auth, we would attempt to reconnect once a second ad infinitum. This changeset ensures that we only reconnect automatically if the socket closed 'normally' as indicated by the code on the socket's CloseEvent. Otherwise, show a 'Websocket closed' error on the inbox view. Ideally we would show a more contextual error (ie, 'Unauthorized'), but unfortunately the actual server response code is not available to our code. It can be observed in the console output from the background page, but programmatically, we only receive the WebSocket CloseEvent codes listed here: https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#Status_codes The websocket error message is displayed by a normally-hidden but ever present socket status element. Clicking this element will immediately refresh the background page, which will try again to open the websocket connection. |
10 years ago | |
|---|---|---|
| .. | ||
| storage | 10 years ago | |
| test | 10 years ago | |
| api.js | 10 years ago | |
| axolotl_wrapper.js | 10 years ago | |
| components.js | 10 years ago | |
| crypto.js | 10 years ago | |
| errors.js | 10 years ago | |
| helpers.js | 10 years ago | |
| libaxolotl_concat.js | 10 years ago | |
| protobufs.js | 10 years ago | |
| sendmessage.js | 10 years ago | |
| storage.js | 10 years ago | |
| stringview.js | 10 years ago | |
| websocket-resources.js | 10 years ago | |
| websocket.js | 10 years ago | |