[matheuszych]

See: https://mantis.ilias.de/view.php?id=47877

The timeline panel header and footer used float-based spacing and shy
buttons with vertical dividers, which produced an uneven layout. Switched
the header to flexbox, aligned footer actions with
ilTimelinePanelFooter, promoted Like and Notes triggers to standard
buttons, removed the separators, and updated related language strings and
styles.

/cc @thojou

[matheuszych]

The changes unfortunately couldn’t be limited to the news module. We also had to update the Like and Notes components to make this work, so you can expect some related changes in other areas as well.

@alex40724 I’d kindly ask you to review these proposed changes.

[fhelfer]

Thank you @matheuszych,

changing the button to standard is definitely the right choice.

However the PR changes like#like from “Like” to “React” / “Reagieren”. That key is shared and must stay the label for the 👍 reaction type, not the popover trigger.

It is still used in:

1. ilLikeGUI::getExpressionText() (components/ILIAS/Like/classes/class.ilLikeGUI.php, ~369) – maps TYPE_LIKE to $lng->txt("like"). Called from ilMembershipCronNotifications::parseNewsItem() (components/ILIAS/Membership/classes/Cron/class.ilMembershipCronNotifications.php, ~301) for course/group notification mails. After this change, thumbs-up reactions appear as “React” / “Reagieren” instead of “Like”.
   Looks like this

Kurs "My Course": "sadfsdf" - sdfsdf
Neue Reaktionen (14)
[dummy5006], 26. Jun 2026, 12:04: Angry
[dummy5003], 26. Jun 2026, 12:04: Laugh
[dummy5002], 26. Jun 2026, 12:04: Love
[dummy5001], 26. Jun 2026, 12:04: Dislike
[dummy5000], 26. Jun 2026, 12:04: Reagieren
[dummy5005], 26. Jun 2026, 12:04: Sad
[dummy5004], 26. Jun 2026, 12:04: Astounded

2. Emoji counter buttons – Button renderer sets aria-label via getSymbolLabel() → txt("like") for the like glyph (with counter).

The trigger button in getHTML() (~140) may use a new key (e.g. react / add_reaction); like should remain for the expression type.

[matheuszych]

Hello @fhelfer ,
thank you for your feedback!

I added a new language variable like#:#react#:#.

Best regards
@matheuszych

[fhelfer]

Thanks, @matheuszych, looks good for the changes to the Like-Component

[matheuszych]

Hello @alex40724 ,
could you please take a look at some of the proposed changes?
Thank you in advance!

Best regards
@matheuszych

[alex40724]

Hi @matheuszych

Thank you a lot for contributing to ILIAS.

Please answer the following questions:

• Which contexts are intended to hide the initial “no comments” message, and why is this behavior changed globally in ilCommentGUI? The PR changes the shared Notes renderer used by Wiki, Blog, DataCollection, and other contexts, although the stated goal is a News timeline layout improvement.
• Could you provide the UI rationale or mockups for removing the empty state and changing the Notes actions? Without this, it is difficult to determine whether the resulting behavior is intended in all these contexts.

Please consider the following suggestions:

• Use an explicit context/behavior flag for suppressing an empty-state message instead of using an empty string from getNoEntriesText() as control flow in getNoteListHTML(). This would keep presentation text separate from the decision whether a caller should render its empty state.

Please implement the following changes:

• Define and preserve the intended empty-list behavior for each shared Notes context before removing notes_no_comments. With the current changes to ilCommentGUI::getNoEntriesText() and getNoteListHTML(), an empty Wiki comment list no longer receives NOTES_LIST at all, and the same behavior affects every other caller using ilCommentGUI.

kindly,
@alex40724

[alex40724]

See comment above.

[matheuszych]

Hallo @alex40724,
first of all thank you for your feedback.

Primarily we intended to change the behaviour of the comments inside of the news timeline but we believe it is a good idea to keep this uniform across every context.

We decided to remove the message because it was causing a visual bug. After further testing with the most recent changes, it seems that said bug does not exist anymore, and thus we can keep the message.

This makes it of course much easier and less invasive.

I reworked some of the changes and made them much slimmer.

Could you please take a quick look again?

Best regards
@mzych

[thojou]

Hey @alex40724,

@matheuszych adjusted the implementation according to your feedback.

Some parts from the earlier review have been changed completely, so there may be some drift from the open objections.

Are there still any open objections from your side?

Kind regards,
@thojou