From 13a7b71e089b93d1bbbcb50d975126837a3c785b Mon Sep 17 00:00:00 2001
From: Travis Ralston <travpc@gmail.com>
Date: Tue, 31 Mar 2020 12:19:17 -0600
Subject: [PATCH] Add a console warning that errors from Jitsi Meet are fine

See diff for info.

We use the fragment to avoid sending conference information to the web server where possible.
---
 src/vector/jitsi/index.ts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/vector/jitsi/index.ts b/src/vector/jitsi/index.ts
index 75b017a269..8be87bbcbf 100644
--- a/src/vector/jitsi/index.ts
+++ b/src/vector/jitsi/index.ts
@@ -96,6 +96,11 @@ function joinConference() { // event handler bound in HTML
     // noinspection JSIgnoredPromiseFromCall
     widgetApi.setAlwaysOnScreen(true); // ignored promise because we don't care if it works
 
+    console.warn(
+        "[Jitsi Widget] The next few errors about failing to parse URL parameters are fine if " +
+        "they mention 'external_api' or 'jitsi' in the stack. They're just Jitsi Meet trying to parse " +
+        "our fragment values and not recognizing the options.",
+    );
     const meetApi = new JitsiMeetExternalAPI(jitsiDomain, {
         width: "100%",
         height: "100%",