[RN] Move preferH264 where it will be in effect (in the future)
This commit is contained in:
parent
4cb36b0a5d
commit
d6d7ce1b67
|
@ -205,9 +205,17 @@ export function createConference() {
|
|||
const conference
|
||||
= connection.initJitsiConference(
|
||||
|
||||
// XXX Lib-jitsi-meet does not accept uppercase letters.
|
||||
room.toLowerCase(),
|
||||
{ openSctp: true });
|
||||
// XXX Lib-jitsi-meet does not accept uppercase letters.
|
||||
room.toLowerCase(),
|
||||
{
|
||||
openSctp: true
|
||||
|
||||
// FIXME I tested H.264 from iPhone 6S during a morning
|
||||
// standup but, unfortunately, the other participants who
|
||||
// happened to be running the Web app saw only black.
|
||||
//
|
||||
// preferH264: true
|
||||
});
|
||||
|
||||
_addConferenceListeners(conference, dispatch);
|
||||
|
||||
|
|
|
@ -39,8 +39,7 @@ const INITIAL_STATE = {
|
|||
// place). Fortunately, these pieces of JavaScript currently involve
|
||||
// third parties and we can temporarily disable them (until we implement
|
||||
// an alternative to async script elements on React Native).
|
||||
disableThirdPartyRequests: true,
|
||||
preferH264: true
|
||||
disableThirdPartyRequests: true
|
||||
},
|
||||
initializationError: null,
|
||||
initialized: false
|
||||
|
|
Loading…
Reference in New Issue