- Jul 12, 2018
-
-
Joas Schilling authored
Signed-off-by: Joas Schilling <coding@schilljs.com>
-
- Jul 11, 2018
-
-
Joas Schilling authored
Signed-off-by: Joas Schilling <coding@schilljs.com>
-
Nextcloud bot authored
-
- Jul 10, 2018
-
-
Joas Schilling authored
Force inactive users to leave the room
-
Joas Schilling authored
Remove additional non-guideline padding in navigation entries
-
Joas Schilling authored
Signed-off-by: Joas Schilling <coding@schilljs.com>
-
Daniel Calviño Sánchez authored
When a user leaves a room the "in call" flag is also reset. As users are now forced to leave the room when they are inactive it is no longer needed to reset the flag using a background job. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
-
Daniel Calviño Sánchez authored
Inactive guests (those that have not sent a ping in the last 30 seconds) are automatically cleaned from a room when the information for that room is got. In the same way, now inactive users are forced to leave the room too when the information for the room is got. Although all inactive guests are cleaned all at once inactive users are forced to leave the room one by one (each one with its own SQL query); although it would be better to force all the inactive users to leave the room at once this should not be a big problem, as users would usually leave the room cleanly; only crashed clients or other exceptional situations should cause a user to be inactive. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
-
- Jul 06, 2018
-
-
Joas Schilling authored
paste only plaintext into the chat input field
-
Nextcloud bot authored
-
- Jul 04, 2018
-
-
Arthur Schiwon authored
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
-
- Jul 03, 2018
-
-
Nextcloud bot authored
-
- Jul 02, 2018
-
-
Nextcloud bot authored
-
- Jul 01, 2018
-
-
Nextcloud bot authored
-
- Jun 28, 2018
-
-
Ivan Sein authored
Fix participants sorting
-
Ivan Sein authored
Add supported Browser list to README
-
Nextcloud bot authored
-
- Jun 27, 2018
-
-
Joas Schilling authored
Signed-off-by: Joas Schilling <coding@schilljs.com>
-
Nextcloud bot authored
-
- Jun 26, 2018
-
-
Ivan Sein authored
Signed-off-by: Ivan Sein <ivan@nextcloud.com>
-
Jan-Christoph Borchardt authored
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
-
- Jun 25, 2018
-
-
Ivan Sein authored
Label button 'Start call' if none is in progress yet, fix #976
-
Jan-Christoph Borchardt authored
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
-
Jan-Christoph Borchardt authored
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
-
Joas Schilling authored
Set "wd_host" using the simulated "selenium.server" variable
-
Nextcloud bot authored
-
- Jun 24, 2018
-
-
Nextcloud bot authored
-
- Jun 23, 2018
-
-
Nextcloud bot authored
-
- Jun 22, 2018
-
-
Daniel Calviño Sánchez authored
The "wd_host" parameter of Selenium2 sessions specify the URL used by the Selenium driver to connect with the Selenium server. Thus, when the Selenium server is at a different host or port than the default one (for example, when run on Drone) the "wd_host" parameter must be set for each of the Selenium2 sessions defined in "behat.yml". Before, this was done by the "run-local.sh" script in the acceptance tests of the server by extending the parameters from the "behat.yml" file, but this prevented adding custom Selenium2 sessions in the acceptance tests of apps (as "run-local.sh" had to know about those sessions). To address that limitation now "run-local.sh" replaces the simulated %selenium.server% variable by the appropriate value in the "behat.yml" file used by the acceptance tests before Behat is run, and thus the "wd_host" parameter must be explicitly included in all Selenium2 sessions. Note that the file that is modified is the one inside the Docker container used to run the acceptance tests, so the original file is not touched. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
-
Ivan Sein authored
MCU integration
-
Joachim Bauch authored
Signed-off-by: Joachim Bauch <bauch@struktur.de>
-
Joachim Bauch authored
The nick name below the avatar is distributed through the DataChannel of the PeerConnection and only sent once during establishment. For the MCU case, the sending PeerConnection is created once and then never changed when more participants join. For this, we periodically send the nick to all other participants through the sending PeerConnection. Signed-off-by: Joachim Bauch <bauch@struktur.de>
-
Joachim Bauch authored
Signed-off-by: Joachim Bauch <bauch@struktur.de>
-
Joas Schilling authored
Simplify check for "action" value in room request.
-
Ivan Sein authored
Remove dead code now that the guest name is no longer shown
-
Nextcloud bot authored
-
- Jun 21, 2018
-
-
Ivan Sein authored
Name change is in Chat, not right sidebar
-
Jan-Christoph Borchardt authored
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
-
Joas Schilling authored
Improve call controls layout to single row
-
Daniel Calviño Sánchez authored
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
-