- 05 Jul, 2019 2 commits
- 04 Jul, 2019 9 commits
-
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
So that the models get removed from the browser cache. Otherwise they get re-fetched when we reconnect.
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
In some cases, it might be desirable to clear cached chat messages once you've reconnected to the XMPP server. For example, if you want to prevent the chat history from getting too long or if you want to avoid gaps in the chat history (for example due to MAM not returning all messages since the last cached message). If you're using OMEMO, then you probably don't want to set this setting to ``true``. OMEMO messages can be decrypted only once, so if they then subsequently get cleared, you won't get the plaintext back.
-
JC Brand authored
and use promises to indicate when an occupant or contact has been set
-
JC Brand authored
This is done to avoid unnecessary repaints and reflows (caused when a message has already rendered and then an occupant is created and attached to that message, cauring a re-render). Related to #1266
-
JC Brand authored
-
- 03 Jul, 2019 1 commit
-
-
Kim Alvefur authored
-
- 01 Jul, 2019 5 commits
- 28 Jun, 2019 3 commits
- 27 Jun, 2019 7 commits
-
-
JC Brand authored
and re-enter if necessary. This solves the problem where we "clone" a tab (e.g. middle-click) and then restore a MUC from cache which we haven't actually entered (given that the new tab represents a new device and session). Also... add `await` in a test to try and fix Travis flakiness
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
We then use this flag to determine whether we should use the values from sessionStorage. This appears to fix the problem I originally tried to fix in 607d7986. When "cloning" a tab (e.g. via middle-click), the `active` flag will be set and we'll create a new empty user session, otherwise it'll be false and we can re-use the user session.
-
JC Brand authored
-
- 26 Jun, 2019 7 commits
- 25 Jun, 2019 6 commits
-
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
Otherwise we run into a bug where two tabs with Converse.js share the same XEP-0198 SM-ID, causing both to go into a reconnection-loop as the XMPP server switches XEP-0198 sessions between them. This bug is due to a distinction in how sessionStorage behaves when you open the existing site in a new tab (e.g. middle-click or `target="_blank"), as opposed to creating a new tab and then opening the site in that tab. In the latter case, the newly created sessionStorage object is empty. In the former, the contents of sessionStorage of the current page is copied over to the new page!
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
otherwise a new cache entry gets created, causing multiple messages to be restored from cache later on.
-