Change Slate Behavior

1 Initial Problem

In ILIAS 6 the slate remains open until it is actively closed.
Somtimes this is good and sometimes not. 

2 Conceptual Summary

The slate behavior should adapt to category of operations.

One case where we assume that it does not work well is navigating out of the slate.
For example into the repository or into the personal workspace.
 
The article is written for the moment to be FeatureFreeze compliant and therefore process compliant.
After an ILIAS 6 stable we want to use eye tracking to check if our assumption is correct.
If so we will support the article and suggest changes. Possible changes would be too big for a bug.
If not, the article will end up in a deep dark hole.

Ich verstehe das nicht, was willst du in welchem Fall?

Ansatz: Das Slate soll nach dem Navigieren geschlossen werden.

• Gegenüberlegung: Gilt das auch für lokale Navigationen im Content, wie im Lernmodul?
• Dann würde die allgemeine Regelung für globale Naviagation gelten.

3 User Interface Modifications

3.1 List of Affected Views

Everywhere the main bar with entries offered.

3.2 User Interface Details

Is it necessary to specify first. Part of the investigation.

3.3 New User Interface Concepts

None. Change of Bahavior.

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 Information

No personal data is stored or processed to implement this feature. 

6 Security Implications

We do not see any changes for special security issues.

7 Contact

• Author of the Request: Samoila, Oliver [oliver.samoila]
• Maintainer: {maintainer}
• 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}.