7 Commits (1f16233afa5db4fc607f66b766d1ca00e51ffda9)

Author	SHA1	Message	Date
Saúl Ibarra Corretgé	a1da6bff1a	[RN] Fix loading config from non-default domains ... When a conference is to happen in a domain which is not the defaut, its config is loaded and set. As part of this process, lib-jitsi-meet is disposed. Because disposing is asynchronous, events happen in this sequence: - set new config - dispose lib (which effectively wipes the config) - init lib This results in the library to be initialized without the loaded config, which was lost. This commit fixes that by delaying setting the config and re-initializing the library until it was disposed.	9 years ago
Lyubo Marinov	0ed85b9d25	Replace features/unsupported-browser SET_UNSUPPORTED_BROWSER with features/base/lib-jitsi-meet SET_WEBRTC_READY ... The error raised by JitsiMeetJS.init() is already in the state of features/base/lib-jitsi-meet so it's not a good design to store the same error in the state of features/unsupported-browser.	9 years ago
Lyubo Marinov	0b9160fb75	LIB_DID_DISPOSE, LIB_DID_INIT, LIB_WILL_DISPOSE, LIB_WILL_INIT	9 years ago
Lyubo Marinov	d2b2f98941	Fix typo	9 years ago
Lyubomir Marinov	52b3eaacb5	[RN] Fix passing config.js to JitsiMeetJS.init	9 years ago
Lyubomir Marinov	4997ae79e3	Fix toolbar's mute buttons when starting muted ... The toolbar's mute buttons depict respective features/base/media states. However, (un)muting is practically carried out by features/base/tracks. When the mobile app enters a conference configured to invite the joining participant to mute themselves, the tracks would be muted but the toolbar's mute buttons would not reflect that.	9 years ago
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 ... As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at 2f23d98424 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	9 years ago