Feature Wiki

Information about planned and released features

Tabs

Responsive Test

1 Initial Problem

The test does not well on small screens. This should be rectified. 
Please check both links ON YOUR MOBILE to experience the current difference:

(A) Question List
(B) Toolbar without any entry outside the hamburger
Issue, Issue, Issue
E Title breaks fine, background pic fine BUT the size of the answer option is ridiulous

2 Conceptual Summary

Responsiveness is an important quality. Tests should work well on small screens.
In the case of test questions this includes that selected answers are clearly highlighted. Yes, we are aware that this is a CSS issue. But we need to state this requirement somewhere.

please ignore that this test displays more than one question per page

3 User Interface Modifications

3.1 List of Affected Views

Presentation of Questions in Test 

3.2 User Interface Details

  • Question List fucks up the scmall screen display entirely. It should be displayed below the question not "half underneath" the question (A)
  • The hamburger is shown in an empty toolbar, at least "Finish the Test" should be visible. It is not THE most important action but actually quite important. (B)
  • Question title does not break on small screens for some question types, for some it is fine.  (C and E) 
  • The size of the Time counter should be stylable in the style editor so it can be layoutet in a fashion that does not eat half the screen on small devices  (C) 
  • Action Menu is almost not operatable on a small screen (C). 
  • We need to make up or mind about the backgound picture: move in or stay out? This is handled diffently with each question type, sigh. (C and D ) 
  • The text of all question types and answer options should break nicely .

Please consider DR 5.1: Issue 15: Presentation problems when running test

3.3 New User Interface Concepts

No. 

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:
  • Maintainer: Killing, Alexander [alex]
  • 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.

7 Discussion

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}.

Last edited: 9. Mar 2022, 13:48, Kergomard, Stephan [skergomard]