Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Communication: Post is not shown correctly when the thread view is opened #10014

Open
HawKhiem opened this issue Dec 13, 2024 · 0 comments
Open

Communication: Post is not shown correctly when the thread view is opened #10014

HawKhiem opened this issue Dec 13, 2024 · 0 comments
Labels
bug communication Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module

Comments

@HawKhiem
Copy link

Describe the bug

Screen.Recording.2024-12-13.123538.mp4

To Reproduce

  1. Go to Communication and click on any channel
  2. Click on the any Reply to a post to trigger the Thread view
  3. Click on another Reply of a different post
  4. See error

Expected behavior

The Thread view should display the correct answer and post

Screenshots

No response

Which version of Artemis are you seeing the problem on?

7.7.5

What browsers are you seeing the problem on?

Chrome

Additional context

No response

Relevant log output

No response
@HawKhiem HawKhiem added the bug label Dec 13, 2024
@github-actions github-actions bot added communication Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module labels Dec 13, 2024
@PaRangger PaRangger moved this from Todo to In Progress in Communication Webclient Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug communication Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module
Projects
Communication Webclient
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HawKhiem