Closed gjaekel closed 1 year ago
This is probably caused by a change in the literals used for the corresponding client configuration option: To my knowledge, the implementation fall back to the full set of features in case of a invalid configuration value.
The task is to check and align the Admin side to reflect the changed requirements of the Jitsi Web-Client (and maybe even add new feature switches).
Sorry, can't reproduce.
Using the current version 1.7.4 of the plugin, the Toolbar configuration feature in the Admin UI becomes unusable: The Jitsi Web-Client will show up all available features and don't reflect the selected set.