[🐛 BUG] Chat control "new message" pop-up is weirdly placed and often inaccessible

[AlexandreSajus]

What went wrong? 🤔

The chat control has a pop-up button saying "A new message is available" when you type a new message and the chat has not auto-scrolled down. Clicking on the button scrolls down to the last message. This pop-up is placed weirdly. For example, here, it overlaps with the chat control:

In another app, it was hidden behind the sidebar:

In another one, it's hidden off-screen:

Expected Behavior

This pop-up should probably be in a fixed position on the page, and it should be laid on top of anything else, like a notification (the ones spawned by gui.notify), for example

Steps to Reproduce Issue

Run this code and type many messages until they fill the screen. The pop-up will appear.

from taipy.gui import Gui
import taipy.gui.builder as tgb

messages = []


def evaluate(state, var_name: str, payload: dict):
    state.messages.append([10, "Loading...", "Robot"])
    state.messages = state.messages


with tgb.Page() as page_home:
    with tgb.layout(columns="1 3", columns__mobile="1"):
        tgb.chat(
            messages="{messages}",
            on_action=evaluate,
            height="80vh",
        )


if __name__ == "__main__":
    gui = Gui(page=page_home)
    gui.run()

Browsers

Chrome

OS

Windows

Version of Taipy

4.0.0

Acceptance Criteria

• A unit test reproducing the bug is added.
• Any new code is covered by a unit tested.
• Check code coverage is at least 90%.
• The bug reporter validated the fix.
• Related issue(s) in taipy-doc are created for documentation and Release Notes are updated.

Code of Conduct

• I have checked the existing issues.
• I am willing to work on this issue (optional)

[sahilborse]

/attempt#2112 please assign me this issue

[FlorianJacta]

@sahilborse You are also assigned here

[github-actions]

This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.

[github-actions]

This issue has been unassigned automatically because it has been marked as "🥶Waiting for contributor" for more than 14 days with no activity.