UI: Interface for Toast Container

[iszmais]

This PR proposes to introduce the UI-Component for implementing Containers for Toasts.
Toast Container:
The Toast Container is a wrapper without direct visual represantation which centralizes the handling and accessebility of Toast components.

A Toast Container can appear in the top right corner , overlaying the ILIAS UI. It can contain and handle Toasts Components and present them to a screen reader. There is not direct way to interact with the Container itself. If the Container does not contain any Toast Components it has no effect on the visual page.

---

The new concept of the Container has the following effect on the existing concept of the Toast (See Toasts):

A Toast can appear in the top right corner, overlaying the ILIAS UI

This ability is omitted since the container decides about the position of apperance.

[iszmais]

@klees @Amstutz

As planned in our meeting i implemented a toast container interface.
I would appreciate if you could take a short look if there is some major issues or differences to your expectation which coudl possibly be prevented before the Jour Fixe

Greetings,
@iszmais

[klees]

It's gonna be me, @Amstutz isn't available this week...

[PurHur]

In the material design of Google which defined the wording "Toast" a toast is a notification without an action.
In the code i see the possibility to attach a link to the toast. Wouldnt that make the Toast to a Snackbar instead? 🍞🍫

Reference: https://material.io/archive/guidelines/components/snackbars-toasts.html

[mjansenDatabay]

In the material design of Google which defined the wording "Toast" a toast is a notification without an action. In the code i see the possibility to attach a link to the toast. Wouldnt that make the Toast to a Snackbar instead? breadchocolate_bar

Reference: https://material.io/archive/guidelines/components/snackbars-toasts.html

Honestly a valid point @PurHur, but the term was defined by the Page Layout Revision (and accepted by the JourFixe) as @iszmais presented this some months ago. Of course this could be renamed in the future if we all decide the name is not appropriate. This has to be discussed with the community, new PRs have to be provided and presented in the JourFixe. This might happen, but not for ILIAS 8 (except if someone wants to provide more 💵 and the ILIAS 8 release will be delayed again).

[PurHur]

I understand your comment. I was just writing that comment, because it was the fist time i encountered these code lines. I understand that this is not the original PR, but i cant look over all comments on all different platforms for the illias development, this is outside of my work scope. This would take tooooo much time. So i just wrote it here to give at least some feedback which could be read. I dont expect that this have any inpact, if you dont like it.
Take that comment as feedback for your JourFix and discuss it there. (Sadly i will not have time monday again)

[klees]

LGTM in general, thanks a lot. I left some inline comments, hope it is ok that I did not leave a fully-fledged review...

[iszmais]

Thx @klees for the review,
i personally actual prefer it that way 😄

Implemented all changed and quashed again.

Grretings,
@iszmais

[matthiaskunkel]

Jour Fixe, 21 FEB 2022 : We highly appreciate this suggestion and accept the PR for ILIAS 8.

[iszmais]

@matthiaskunkel thanks for the appreciation!

@klees feel free to merge or to give some minor feedback if needed.

[Amstutz]

Hi @iszmais

Thx a lot for providing the interface along with the examples.

This seems all fine. We merge this to proceed to the next step. We are looking forward to review the implementation.

Thx
@klees and @Amstutz