Replace Tables with Responsive Elements

1 Initial Problem

Many a screen in ILIAS uses a table to present a huge amount of data. These tables do not colapse on small screens.

2 Conceptual Summary

The screens comprising tables to handle a lot of data should not require scrolling left to right. Those screens should only requiring scrollingup and down.

3 User Interface Modifications

3.1 List of Affected Views

• Course > Members > Edit Participants
• Course > Members > Memberships in Groups
• Course > Learning Progress > Course Participants
• Group > Members > Edit Participants
• Group > Learning Progress > Course Participants
• Mediacast > Learning Progress > Users
• Administration > System Settings and Maintenance > Languages > Settings

3.2 User Interface Details

The existing tables are replaced by the appropriate KS element.

Table

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

From the accessibility point of view what we call a table is a grid and the do some implications come with that territory.

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 Privacy

No new or other data used, thus no new privacy issue.

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• 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.}

8 Funding

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

• …

9 Discussion

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