And use it instead of listening to multiple Promises.

Promises get resolved once, which means using them doesn't work for
cases where the user logs out, and then in again (because the handlers
don't get called upon 2nd login).

* Update jslicenses-inverse.html

* Update inverse.html

* Update index.html

* Update mobile.html

* Update anonymous.html

* Update CHANGES.md

It depends on `eval` which is unsafe.

Otherwise we lose the MUC session upon reload.

when using converse.js inside a webcomponent

* Translated using Weblate (German)

Currently translated at 94.0% (268 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/de/

* Translated using Weblate (Chinese (Traditional))

Currently translated at 35.7% (102 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/zh_Hant/

* Translated using Weblate (German)

Currently translated at 98.9% (282 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/de/

* Translated using Weblate (Russian)

Currently translated at 60.3% (172 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/ru/

* Translated using Weblate (French)

Currently translated at 100.0% (285 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/fr/

* Translated using Weblate (Russian)

Currently translated at 100.0% (285 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/ru/

* Translated using Weblate (Portuguese (Brazil))

Currently translated at 90.5% (258 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/pt_BR/

* Translated using Weblate (Portuguese (Brazil))

Currently translated at 91.2% (260 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/pt_BR/

* Translated using Weblate (Portuguese (Brazil))

Currently translated at 100.0% (285 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/pt_BR/

* Translated using Weblate (Russian)

Currently translated at 100.0% (285 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/ru/

* Translated using Weblate (Portuguese (Brazil))

Currently translated at 100.0% (285 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/pt_BR/

* Translated using Weblate (Ukrainian)

Currently translated at 60.3% (172 of 285 strings)

Translation: Converse.js/Translations
Translate-URL: https://hosted.weblate.org/projects/conversejs/translations/uk/

1. Add a new `view_mode` value: `embedded`.

   This value is used to determine wether the `converse-muc-embedded`
   plugin is active or not.

2. Remove the need for the #converse-embedded-chat element.

   Instead we reuse the #conversejs element and embed inside that.

3. Removed the need to manually blacklist core plugins

   This is now done automatically if `view_mode` is set to `embedded`.
   Perhaps eventually we don't blacklist at all and instead use the
   `enable` plugin method. For some that probably won't work, like
   `converse-chatview`, which we still need to be active.

Setting it on `window` is necessary to have it available inside a
webcomponent.

Triggering an event is necessary so that we don't call
`converse.initialize` too early.

Needed when converse.js is included inside a webcomponent.
The fonts.css file is then copied over to the host DOM.

Necessary due to this bug:
  https://bugs.chromium.org/p/chromium/issues/detail?id=336876

We have bedroom, bathroom, classroom and boardroom as one word.
Living room is spelled separately because of the present participle (+ing) in living.

With "chatbox" it's a bit more subjective.
We have chatbot as one word (but litter box as two).
For consistency with chatroom, I'll go with one word.

which we check by checking if the PEP identity is provided.
https://xmpp.org/extensions/xep-0163.html#support

Also, the condition was the opposite of what it should have been.