Default value for useComputedState is undefined but treated as true
value.
#4918
Labels
core
The issue is caused by the editor core code.
good first issue
Relatively easy to fix. This is a perfect issue if you are willing to create a Pull Request.
plugin:justify
The plugin which probably causes the issue.
plugin:list
The plugin which probably causes the issue.
status:confirmed
An issue confirmed by the development team.
type:bug
A bug.
Milestone
Type of report
Bug
Provide detailed reproduction steps (if any)
Documentation says that default value for useComputedState is
true
. However, there is no place in the code that assignstrue
to this config option.This option is used in
justify
plugin, which interprets theundefined
value astrue
:ckeditor4/plugins/justify/plugin.js
Line 12 in 728e192
This option is used in
bidi
plugin, which interprets theundefined
value astrue
:ckeditor4/plugins/bidi/plugin.js
Line 18 in 728e192
This option is used in
list
plugin, which interprets theundefined
value astrue
:ckeditor4/plugins/list/plugin.js
Line 367 in 728e192
Please note, that there are few other lines in those plugins, that use this 'trick'.
Code logic makes the value of
config.useComputedState
interpreted the same as the documentation says: astrue
value. However, If the user tries to useconfig.useComputedState
, he will getundefined
instead oftrue
.Expected result
What is the expected result of the above steps?
Plain
config.useComputedState
config option is equal totrue
.Actual result
What is the actual result of the above steps?
Plain
config.useComputedState
config option is equal toundefined
and interpreted astrue
.Other details
The text was updated successfully, but these errors were encountered: