pad: Fix application of padOptions
values from settings.json
This commit is contained in:
parent
f8b4189bc4
commit
99fae2ec6e
2 changed files with 7 additions and 1 deletions
|
@ -2,6 +2,12 @@
|
|||
|
||||
### Notable enhancements and fixes
|
||||
|
||||
* The following settings from `settings.json` are now applied as expected (they
|
||||
were unintentionally ignored before):
|
||||
* `padOptions.lang`
|
||||
* `padOptions.showChat`
|
||||
* `padOptions.userColor`
|
||||
* `padOptions.userName`
|
||||
* Fixed a potential attribute pool corruption bug with `copyPadWithoutHistory`.
|
||||
* Mappings created by the `createGroupIfNotExistsFor` HTTP API are now removed
|
||||
from the database when the group is deleted.
|
||||
|
|
|
@ -148,7 +148,7 @@ const getParams = () => {
|
|||
let value = clientVars.padOptions[setting.name];
|
||||
if (value == null) continue;
|
||||
value = value.toString();
|
||||
if (value === setting.checkVal) {
|
||||
if (value === setting.checkVal || setting.checkVal == null) {
|
||||
setting.callback(value);
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue