bb45f76a7a
Initializing UI features, like keyboard shortcuts, by chaining onto APP.conference.init is not safe because init can fail, skipping the initializing of UI features. This can happen when the room is locked and then a failure event is dispatched into middleware. I couldn't find a place to properly chain onto in the APP.conference.init promise chain, primarily due to the flow continued within middleware, so instead I leveraged an existing listener for CONFERENCE_JOINED. |
||
|---|---|---|
| .. | ||
| actionTypes.js | ||
| actions.native.js | ||
| actions.web.js | ||
| functions.js | ||
| index.js | ||
| reducer.js | ||