Skip to content

Conversation

@Rillke
Copy link
Contributor

@Rillke Rillke commented Jan 16, 2026

The value of the text area will be stored in database. When the pain(t) question loads, it will populate the text area with an initial value. That textarea value does not need to have back- slashes extra escaped as opposed to the string that is assigned as a JavaScript variable.
This usually has no implications: ILIAS only sends the textarea value if an answer has changed and an answer only changes if some- one has edited the canvas and therefore the logic has already updated the textarea with "normal" (i.e. not double-escaped) JSON it was initialized with.
Now, if you install a certain patch provided by databay AG that restores the feature that answers are saved during question list navigation at all, the patch will store the question's answer, no matter if the answer has changed after loading from DB.


I guess you can remove the whitespace changes, if you'd like to, yourself. Editor is told to remove trailing whitespace for compliance with other projects.

The value of the text area will be stored in database. When the
pain(t) question loads, it will populate the text area with an
initial value. That textarea value does not need to have back-
slashes extra escaped as opposed to the string that is assigned
as a JavaScript variable.
This usally has no implications: ILIAS only sends the textarea
value if an answer has changed and an answer only changes if some-
one has edited the canvas and therefore the logic has already
updated the textarea with "normal" (i.e. not double-escaped) JSON
it was initialized with.
Now, if you install a certain patch provided by databay AG that
restores the feature that answers are saved during question list
navigation at all, the patch will store the question's answer,
no matter if the answer has changed after loading from DB.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant