Show Advanced KnowledgeHide Advanced Knowledge

Column Layout : Same Height for all Blocks

1 Initial Problem

Creating a column layout with coloured sections is pain in the ass. The height of each section is defined by the content of a section. And if there are three sections with coloured background and  a picture and some text included, it is almost impossible to get all with the same height (even if entering protected spaces or using other workarounds). Unfortunately, a column layout where sections with background have different heights never looks really good...

2 Conceptual Summary

There should be an option to force all sections within one row of a column layout to have the same height - at least the height of the heighest section. Probably, this is only possible by some JS magic. This behaviour should be an option of the column layout and not the general case (in other scenarios, sections with different heights might be appreciated and expected).

Kunkel, Matthias [mkunkel]: Two aspects have to be clarified:

1. Do we want to have both behaviours - (a) embedded blocks take all height available in the column row and (b) blocks behave like at the time being (height is determined by embedded content) - AND
2. if (a) which object is responsible for this behaviour: column layout OR block

Only if this has been clarified we know where the setting has to be presented: (1) in column layout settings or in (2) block settings.

3 User Interface Modifications

3.1 List of Affected Views

• ILIAS page editor » Insert column layout » Settings (in case of 1)
• ILIAS page editor » Insert block » Settings (in case of 2)

3.2 User Interface Details

The preferred look of a column layout with embedded blocks is as follows:

3.3 New User Interface Concepts

No new user interface.

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

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

• ILIAS-Verein

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