Attempts to fix this race condition:
1. Web client joins a conference.
2. Electron client joins the same conference.
3. Web client requests capabilities of Electron
   using version 1111.
4. Electron adds remote control capability,
   settings its version to 2222.
5. Electron responds to web client's requests
   but with features of 2222.
6. Web client caches request under 1111.
7. Any future calls to get features for a client
   with version 1111 will incorrect include the
   remote control capability.

Attempts to fix the following issue:
1. Electron user starts the conference join process.
2. Electron user adds remote control capability and
   attempts to send presence.
3. Electron user presence send is blocked because the
   conference has not been joined.
4. Electron user joins the conference.
5. The remote control capability is not emitted until
   some other presence change triggers another
   presence send. Until then, other uses will not see
   remote control option available for the electron
   user.

* Updates kicked event to inform local and remote kicks and who it affects

* Parses actor from MuteIQ and adds participant info to mute track event.

* Fixes emitting both events.

* Fixes comments.

The idea is to not show the frozen video indication for intermittent
failures which can be confusing to users.

* Add error description

* Change error message

* Change error message

Update API.md

* Removes Edge support.

* Removes unused dependency.

In TraceablePeerConnection: we're no longer injecting a recvonly SSRC
when the local video track is muted, so it's normal that there is no
SSRC found in the local SDP when it's muted.

About RTPStatsCollector: at the time of adding this log statement a case
was missed when local audio track could be replaced in the P2P
connection when a new audio device is selected.

1. JitsiMeetJS.createLocalTracks constraints missing data.
2. removed duplicate documentation for selectParticipant.
3. added setReceiverVideoConstraint function data.

* fix(permissions): remove space from requesting camera

Chrome errors on querying permissions with "camera "
because it does not match an expected enum.

* fix(permissions): check value of returned PermissionStatus

A permissions query returns an object with a status/status
of whether or not permission has been granted. Check that
value in addition to the existence of the object.

* fix(permissions): prevent permission being set to undefined

* ref(permissions): move permissions strings to constants

eslint-config-jitsi 1.0.0

jitsi-meet-spot currently supports mobile browsers. A
line should be drawn somewhere but maybe not here.
Chrome iOS does not have navigator.mediaDevices so add
a truthy check before checking for getDisplayMedia.

Spot is the consumer of screensharing using a camera
input and through a proxy connection. To differentiate
which one is active, declare a source type on the
created "desktop" stream.

A camera source can be used as a screenshare source.
Normally for screenshare resolution is not capped and
the same will be true for the fake screenshare source.

Adds a flag which can be used to disable talking to Jicofo. It's
intended to be used only in jitsi-meet-spot which joins a special room.

Actually pass in the option to getTrackSSConstraints so it gets
applied to the desktop track.

Supported since Firefox 66.

Because it's possible to go back from ICE FAILED state to CONNECTED it's
better to give it some time until the XMPP connection recovers and only
if they ICE does not recover in time send the ICE failed notification
to Jicofo. It's done by sending a ping to the XMPP server and checking
the ICE after 2 seconds past the ping successful response.

Make the client send ICE failed notification to let Jicofo know
that the ICE connection with the bridge has failed. It can then
re-create the channels and send new transport in the
'transport-replace' message to give it another try.

Also adds a bridge session ID so that Jicofo can discard outdated
requests. When a bridge dies multiple clients may send ICE failed
notifications at the same time. Jicofo will detect bridge failure
when processing the first one and it must not act on the following
requests for the broken bridge session which is no longer current.

A bridge session ID will be sent in new 'bridge-session' XML element
which is part of either 'session-initiate' or 'transport-replace'
message. The server's region is moved to this element as well as
it's part of a bridge session.

It should be provided by the environment, just like on web. This avoids bundling
callstats on web, where it won't be used (we dynamically download it).

This reduces the bundle size from about 1MB to 675KB, almost 40%.

* feat(screenshare): support remote wireless screenshare

- ProxyConnectionService is exposed and meant to be the
  facade for creating and updating a peer connection with
  another peer, outside of the muc.
- ProxyConnectionPC wraps JingleSessionPC so the peer
  connection handling can be reused.

* attempt to make more configurable