320e67baa1
The counterpart of the external API in the Jitsi Meet Web app uses the search URL param jwt to heuristically detect that the Web app is very likely embedded (as an iframe) and, consequently, needs to forcefully enable itself. It was looking at whether there was a JSON Web Token (JWT) but that logic got broken when the JWT support was rewritten because the check started happening before the search URL param jwt was parsed.
81 lines
2.4 KiB
JavaScript
81 lines
2.4 KiB
JavaScript
/* application specific logic */
|
|
|
|
import "jquery";
|
|
import "jquery-contextmenu";
|
|
import "jquery-ui";
|
|
import "strophe";
|
|
import "strophe-disco";
|
|
import "jQuery-Impromptu";
|
|
import "autosize";
|
|
|
|
import 'aui';
|
|
import 'aui-experimental';
|
|
import 'aui-css';
|
|
import 'aui-experimental-css';
|
|
|
|
window.toastr = require("toastr");
|
|
|
|
import conference from './conference';
|
|
import API from './modules/API';
|
|
import keyboardshortcut from './modules/keyboardshortcut/keyboardshortcut';
|
|
import remoteControl from "./modules/remotecontrol/RemoteControl";
|
|
import settings from "./modules/settings/Settings";
|
|
import translation from "./modules/translation/translation";
|
|
import UI from "./modules/UI/UI";
|
|
|
|
const APP = {
|
|
API,
|
|
conference,
|
|
|
|
/**
|
|
* After the APP has been initialized provides utility methods for dealing
|
|
* with the conference room URL(address).
|
|
* @type ConferenceUrl
|
|
*/
|
|
ConferenceUrl: null,
|
|
|
|
// Used by do_external_connect.js if we receive the attach data after
|
|
// connect was already executed. status property can be "initialized",
|
|
// "ready" or "connecting". We are interested in "ready" status only which
|
|
// means that connect was executed but we have to wait for the attach data.
|
|
// In status "ready" handler property will be set to a function that will
|
|
// finish the connect process when the attach data or error is received.
|
|
connect: {
|
|
status: "initialized",
|
|
handler: null
|
|
},
|
|
connection: null,
|
|
|
|
// Used for automated performance tests
|
|
connectionTimes: {
|
|
"index.loaded": window.indexLoadedTime
|
|
},
|
|
keyboardshortcut,
|
|
|
|
/**
|
|
* The log collector which captures JS console logs for this app.
|
|
* @type {LogCollector}
|
|
*/
|
|
logCollector: null,
|
|
|
|
/**
|
|
* Indicates if the log collector has been started (it will not be started
|
|
* if the welcome page is displayed).
|
|
*/
|
|
logCollectorStarted : false,
|
|
remoteControl,
|
|
settings,
|
|
translation,
|
|
UI
|
|
};
|
|
|
|
// TODO The execution of the mobile app starts from react/index.native.js.
|
|
// Similarly, the execution of the Web app should start from react/index.web.js
|
|
// for the sake of consistency and ease of understanding. Temporarily though
|
|
// because we are at the beginning of introducing React into the Web app, allow
|
|
// the execution of the Web app to start from app.js in order to reduce the
|
|
// complexity of the beginning step.
|
|
import './react';
|
|
|
|
module.exports = APP;
|