Feature Wiki

Information about planned and released features

Tabs

Content Tab for Poll

1 Initial Problem

To users without 'Edit Settings' permission, Polls are exclusively shown in their parent Container object. For these users Polls can not be entered, they do not have a context of their own. This limit its the Poll in some respects, e.g. permalinks to it instead lead to its parent container, and makes it behave differently than all other ILIAS objects.

Further, only appearing in the context of its container makes it harder to show the results of a poll e.g. in a presentation or lecture setting.

2 Conceptual Summary

Polls should have a 'Content' tab, where the what is shown as the content of the Poll block is shown on its own as the main content of the page. Permanent links should link to this tab, instead of the parent Container. The tab should be accessible by all users with 'Read' permission of the Poll.

3 User Interface Modifications

3.1 List of Affected Views

  • Poll > Content

3.2 User Interface Details

The new 'Content' tab should have the same content as the Poll block, except for the Poll's description and its availability, as this information is already contained in the Poll's header.

The content should be left aligned, and stretch to about a third of the available space. The question and answers should be scaled up slightly, similar to questions in Tests.

If results are shown, they should dynamically update if new votes are cast, reloading the page should not be necessary.

Alternatively, one could also show the content centered, with limited width.

3.3 New User Interface Concepts

To have content not take up all the space it has is slightly unusual in ILIAS. Here we believe it to be justified, such that the two different presentations of Polls (block and 'Content' tab) do not look too different from each other. In the long run, a 'Question' KS component should be developed that works for both occasions (as well as in Surveys, Tests, etc.).

3.4 Accessibility Implications

No accessibility implications.

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

-

4.3 Privacy

No changes required to the privacy information.

4.4 Security

No foreseeable security implications.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Schmitz, Tim [tschmitz]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

JourFixe, ILIAS [jourfixe], 04 MAR 2024: We highly appreciate this suggestion and accept the feature for ILIAS 10 - with the small change to align the content in the Content tab left (as shown in the accordeon).

Kunkel, Matthias [mkunkel], 30 JUL 2025: Can we have a headline for the presentation of results (if it is shown depending on the settings)? It would make things a bit a clearer (and probably even helpful for screenreaders).

Schmitz, Tim [tschmitz], 04 AUG 2025: Sure, a header for the results seems like a reasonable addition. It would make sense to then add it to both modes of presentation (content tab and in the block).

JourFixe, ILIAS [jourfixe], 04 AUG 2025: We highly appreciate this suggestion and accept the feature for trunk. We prefer a left-aligned presentation of questions and results, incl. a headline for the results. The width of the presented bar chart should be limited to avoid its presentation on the full screen width.

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.

Last edited: 4. Aug 2025, 15:47, Kunkel, Matthias [mkunkel]