When switching conversations, the participant list's scroll container is
scrolled back to the top instead of keeping an arbitrary position.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Only display a warning when leaving the page completely, which would
abort pending sending operations.
Switching between conversations will keep sending in the background so
no warning is needed.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Rely on the event chain from the components instead of listening to
native events. The latter's problem is that it would also fire when the
user is clicking on the three dots menu.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Disable avatar menu in conversation lists to avoid interaction glitches.
The only place where it's enabled currently is in the top bar.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Move the conversation icon outside of the conversation header so that it
doesn't get cut.
Fixes issue where the status icon was cut.
Fixes issue where clicking the avatar would open the settings dialog
instead of the avatar menu.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Receiver only peers do not handle local track changes, so there is no
need to trigger the processing of pending replace track actions in that
case, as there will be none.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Besides reacting to disable state changes the sent streams are also
stopped now when tracks are initially disabled and no event is emitted.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
In order to stop the sent streams the track can be replaced in the
sender by a null track. To differentiate between a null track due to no
device being selected or the original track being stopped an additional
attribute, "trackDisabled", is attached now to each sender.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
If "processPendingReplaceTracks" was called while a processing was
on-going (for example, on quick connection state changes) this would
cause another processing in parallel, which could have unexpected
results.
To prevent that now there is at most a single processing on-going at any
time. The method also returns a promise now, which will make possible to
enqueue further actions after the processing has finished even if the
processing was actually started in a different call.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
If a connection has not started yet tracks can not be replaced, as
Firefox will get "stuck" and not replace the tracks even if tried later
again once connected.
To address that now the tracks are replaced only when the connection is
not in the "new" state (even if the connection is in the "checking"
state replacing the track seems to work fine). If a track is tried to be
replaced in the "new" state the action is enqueued and executed once the
connection is started.
Besides that as the replace track actions are now enqueued this also
prevents replacing a track before the previous replacement has finished.
This should not happen, but if it did it could have caused issues due to
the track to be replaced not having been set yet.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Don't set focus on message element when scrolling to the first unread
message as this conflicts with focusInput() from the message form.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
The viewer expect the "files:sidebar:opened" and "files:sidebar:closed"
events to be emitted on Nextcloud bus to adjust its width based on the
sidebar.
Both events could be emitted by directly listening to AppSidebar events
on RightSidebar. However, for now only the "closed" event is listened;
the "opened" event does not seem to work reliably (it seems that
sometimes it is emitted before the sidebar has finished opening, so the
viewer ends overlapping the sidebar due to getting its width when it is
not fully opened), so for now the custom detection of when the sidebar
has finished opening is still used.
In Talk the sidebar events are currently needed only by the viewer, and
when the viewer is opened the sidebar will be opened only by the viewer
through "OCA.Talk.Sidebar.open()", so not emitting the sidebar events
directly on the RightSidebar component should not be a problem.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Use margin-top to avoid overriding the top value which has different
values depending on how many notifications are visible.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
In Nextcloud 22 "setFullScreenMode" was added to OCA.Files.Sidebar. This
method is expected and used by the viewer, so even if the sidebar style
is not changed to set it in full screen mode the method needs to be
there.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Joas Schilling
Nextcloud bot
Vincent Petry
Joas Schilling
Daniel Calviño Sánchez