- 11 Oct, 2018 8 commits
-
-
JC Brand authored
And fix an HTML rendering bug for info messages and nicks that contain spaces
-
JC Brand authored
Previously we checked only if the last message was a join message from the same person. Now instead we check the last n messages that are join or leave notifications.
-
JC Brand authored
* Don't show leave notification twice when someone leaves, joins and then leaves again * Add a test case for a member joining and then leaving
-
JC Brand authored
-
JC Brand authored
Fixes #1169
-
JC Brand authored
-
JC Brand authored
Seems to make some sense after all, but we need to add a check that the user isn't a roster contact as well.
-
JC Brand authored
The second especially doesn't make sense and I'm currently not aware of a case headline stanzas with a JIDs containing `@` and with a body exist.
-
- 10 Oct, 2018 5 commits
- 09 Oct, 2018 1 commit
-
-
Licaon_Kter authored
* Typo in error message
-
- 08 Oct, 2018 1 commit
-
-
JC Brand authored
-
- 07 Oct, 2018 4 commits
- 06 Oct, 2018 6 commits
- 05 Oct, 2018 9 commits
-
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
Hide "add contact" button and requesting/pending contacts when allow_contact_requests is false.
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
We were removing the disco entity, but it's associated collections (`features`, `fields`, `identities` etc) were still stored in localStorage and not cleared. So when the entity gets recreated, the stale localStorage cached items repopulate the collections. Added `refreshFeatures` API method for refetching disco features and use that instead.
-
JC Brand authored
-
- 03 Oct, 2018 1 commit
-
-
JC Brand authored
`toLocaleString` now returns element attributes in alphabetical order (for better cross-browser consistency). Also, `toLocaleString` is now used in favor of `outerHTML` because browsers aren't consistent with one another in their output.
-
- 02 Oct, 2018 5 commits
-
-
JC Brand authored
-
JC Brand authored
Otherwise compatibility with Conversations is broken. Unfortunately this means that OMEMO won't work on Edge, because it for some reason requires the additionalData. References: * https://github.com/conversejs/converse.js/issues/1187#issuecomment-426276243 * https://stackoverflow.com/questions/42933162/web-crypto-api-using-microsoft-edge-38-14393-0-0/42950731 Fixes #1187
-
JC Brand authored
-
JC Brand authored
-
Emmanuel Gil Peyrot authored
Currently translated at 99.7% (338 of 339 strings) Translation: Converse.js/Translations Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/fr/
-