Questions (Test, Testpool, ILIAS-LM) - Show Javascript-Code as Text

1 Initial Problem

ILIAS-LM-authors or ILIAS-Test authors miss the functionality to add Javacript-code (or other code) in the answers of a question.

• Actually, ILIAS parses the <javascript>-Code
• So they have to write the code manually, or they have to use external tools (see the following "Javascript-Example"

Javascript-example

In the answer-field of a question (ILIAS-test, ILIAS-Test-Pool and ILIAS-Learning-Module), ILIAS parses e.g. the following code when the author saves the question:

The author writes:
<script type="javascript">JAVASCRIPT CODE</script>

ILIAS parses the Code, and in the answer-field, the following text remains
JAVASCRIPT CODE

2 Conceptual Summary

ILIAS should not show the escaped version of content encaspulated by tags such as "script" or "javascript" (or similar). It should display the original version of the content. For security reasons, there should be no way to run this code. 

The author writes:
<script type="javascript">JAVASCRIPT CODE</script>

ILIAS could e.g. convert to:
<script type="javascript">JAVASCRIPT CODE .....

But show the user the output:
<script type="javascript">JAVASCRIPT CODE</script>


Affected objects:

• ILIAS Learning Module
• ILIAS Test
• ILIAS Testpool
• also occurs in Survey

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Lauener, Hansjörg [lauener]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Universität Bern

7 Discussion

Heyser, Björn [bheyser], 29 May 2017: I had a talk with Hansjörg Lauener. For the moment the enduser should be happy with the existing feature spectrum. 

Indeed the requirement is fullfilled for all question types supporting the TinyMCE for the input of answer options. Extending other question types to support this should not be the general strategy. In the long run there should be any possible concept to make use of the page editor for handling answer option contents with all question types, as the page editor is the desired content editing tool.

Kergomard, Stephan [skergomard], 2022 Mar 9: We close this as part of the cleaning up effort undertaken in the Splitting-Up Test & Assessment Workinggroup.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.