- 10 May, 2019 1 commit
-
-
JC Brand authored
-
- 09 May, 2019 2 commits
- 08 May, 2019 2 commits
- 07 May, 2019 2 commits
- 06 May, 2019 5 commits
- 05 May, 2019 1 commit
-
-
laszlovl authored
Messages (received directly or via MAM) are stored in a backbone collection that's kept sorted by the message's "time" attribute. Various parts of the codebase rely on this behavior. For regular messages, the time attribute is generated by `moment().format()`, which generates a timestamp in the browser's local timezone, for example "...+02:00". For MAM messages, we would previously copy the "delay.stamp" value into the "time" attribute verbatim. However, that value is generated by the server and is unlikely to be in the same timezone locale. ISO timestamps expressed in different timezones cannot be sorted lexicographically, breaking the premise of keeping the messages collection sorted by time.
-
- 03 May, 2019 6 commits
-
-
JC Brand authored
instead of accepting a callback functions.
-
JC Brand authored
Room auto-configuration broke if the config form contained fields with type `fixed`
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
Legitimate carbons messages blocked due to erroneous forgery check
-
supun19 authored
* Rooms Api number of parameters in the documentation was made 2 from 3 as api which is used to open a room with default configuration has only 2 parameters.
-
- 02 May, 2019 3 commits
- 29 Apr, 2019 3 commits
- 27 Apr, 2019 3 commits
- 25 Apr, 2019 3 commits
- 24 Apr, 2019 4 commits
-
-
JC Brand authored
-
JC Brand authored
-
JC Brand authored
That way we don't lose the user's input values, we avoid flashing and we avoid unnecessary rendering. In the process, fixed an annoying issue where Chrome auto-completes what it thinks is the username into the "Language Tag" field of the MUC config form. Instead we tell Chrome that the MUC JID is the username, thereby also letting it save the password to to that JID.
-
JC Brand authored
-
- 23 Apr, 2019 5 commits