jiti-meet/modules
Leonard Kim b86df7a8e3 fix(remote-control): do not assume failed query is missing support
Multiple requests for checkUserRemoteControlSupport can be in
flight simultaneously. Order of promise resolution is not
guaranteed. It is possible for Request A and Request B to be
in flight and then Request B's promise chain resolves first.
Request A could have encountered errors and then resolve. Then
what could happen is checkUserRemoteControlSupport returns true
for remote control support due to Request B and the UI updates.
But then checkUserRemoteControlSupport returns false for
remote control support due to Request A's error and the UI
updates to hide remote control.
2019-07-11 07:25:08 +01:00
..
API feat(api): add notifications for kicked participants 2019-07-01 12:53:25 -07:00
UI fix(remote-control): do not assume failed query is missing support 2019-07-11 07:25:08 +01:00
devices feat(api): notify api of mic and camera errors (#4289) 2019-05-29 14:17:07 -07:00
keyboardshortcut feat(chat): convert to use React 2018-09-26 14:48:10 -05:00
keycode feat(eslint): Enable for non react files 2017-10-16 14:36:29 -05:00
recorder feat(eslint): Enable for non react files 2017-10-16 14:36:29 -05:00
remotecontrol fix(remote-control): do not assume failed query is missing support 2019-07-11 07:25:08 +01:00
translation ref(i18next): Remove the base/config dependancy. 2018-05-18 13:34:08 -05:00
transport ref(toolbar): remove contact list 2018-04-10 09:34:52 +02:00
util ref(JitsiMeetLogStorage): move to base/logging 2019-02-01 10:34:03 +01:00