When two or more consecutive messages were sent by the same participant
with a difference of less than 120 seconds between each message those
messages are now shown grouped (the participant name is not shown for
the intermediate messages and each message is pushed closer to the
previous message).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The button is updated when the model changes, but the model was not
being synced when the user joined or left a call, so it only changed
when it was synced for any other reason.
Fixes#473
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When there is no password input field its value is undefined, so the
rendering never finished when calling "renderWhenInactive" due to the
strict equal comparison.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The standard Nextcloud header is added automatically outside the
"#app-content" element when using the "user" template, so it is
automatically hidden when "#app-content" is set to fullscreen mode. The
public page uses the "base" template, so it has to provide its own
header element; this element appears inside "#app-content" (probably to
make it transparent using CSS rules during a call), so it has to be
explicitly hidden when in fullscreen mode.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Since commit 3470d0a44e in Nextcloud
server the HTML element for the logo must include the "logo" CSS class
to be shown.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Since commit eae71a3977 a participant
(user or guest) can be in a room without joining a call; since then
sessions are no longer set and passwords are no longer checked when
joining a call, but when joining a room. Due to this some integration
tests had to be modified to join a room instead of a call.
Note, however, that in the modified tests there is no need to join a
call too once the participant has joined the room, as they either test
joining the room itself (the password tests) or the tested actions
simply need the participant to be in a room (the chat tests). Moreover,
in this later case, note that a participant is in a room if she created
a room, was invited to it or explicitly joined it, so the chat tests
involving a participant creating a room or inviting another one to it
did not need to be modified.
Finally, neither the call tests nor the "userJoinsCall" method from
FeatureContext were modified yet, as it has to be decided first whether
directly joining a call also joins the room automatically or not.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This fixes a UI issue with the standalone signaling where the interface
didn't switch back to the "Looking good" view when leaving a room.
Signed-off-by: Joachim Bauch <bauch@struktur.de>