jiti-meet/modules/remotecontrol
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
..
.eslintrc.js Remote control - display the authorization dialog in meet (#1541) 2017-05-03 18:57:52 -05:00
Controller.js Upgrade NPM dependencies/packages: react-native 0.50 2017-12-04 00:45:18 -06:00
Receiver.js fix(lib-jitsi-meet): Use the exported constants 2017-10-13 09:50:48 -05:00
RemoteControl.js fix(remote-control): do not assume failed query is missing support 2019-07-11 07:25:08 +01:00
RemoteControlParticipant.js feat(remotecontrol): Prevent multiple remote control sessions (#1875) 2017-08-17 09:43:22 -07:00