KS-Entry: Interruptive Modal

1 Guideline

• Name: Interruptive Modal
• DOM, LESS, JS / Screenshot*: Todo
• PHP Class: ilModalGUI
• PHP Example:
• External Library: Bootstrap Modal
• Status of Entry: Proposed
• Status of Implementation: to be implemented
• Description*:
  • Purpose: An Interruptive Modal disrupts the user in critical situation, forcing him or her to focus on the task at hand.
  • Composition: The Modal states why this situation needs attention and may point out consequences.
  • Effect: All controls of the original context are inaccessible until the Modal is completed. Upon completion the user returns to the original context.
• Background:
• Context*: Interruptive Modals are currently used to submit or delete answers in a test before turning to using the test-related controls.
• Rules:
  • Due to the heavily disruptive nature of this type of Modal it MUST be restricted to critical situations (e.g. loss of data).
  • All delete-actions are critical situations and MUST be implemented as an Interruptive Modal.
  • Interruptive Modals MUST contain a Default Button continuing the action that initiated the Modal (e.g. Delete the Item) on the left side of the footer of the modal and a button canceling the action on the right side of the footer as Default Button.
  • The Cancel Button in the footer and the Close Button in the header MUST NOT perform any additional action than closing the confirmation screen.
• Relations:
  • Is A: KS-Entry: Modal

2 Todo in ILIAS 5.2

• KS-Todo: Interruptive Modal: All confirmation screens are to be performed as Interruptive Modal.

3 Status

• Effective from release: ILIAS 5.2
  
• Approved by Jour Fixe at: JourFixe-2015-12-07
• Implementation status: needs implementation
  
• Funding for streamlining existing features: { name of organisation }
• Implementation of guideline: { all developers | name of responsible developer }

4 Components that are not compliant with the Guideline

• …

5 Discussion

JourFixe, ILIAS [jourfixe], Dec 07, 2015: Accepted by Jour Fixe. Related feature requests should be added to wiki (todo...) and presented to JF for final acceptance.