Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

75%
+4 −0
Q&A Threaded comments are here!

posted over 1 year ago by Lundin‭  ·  edited 12mo ago by Monica Cellio‭

Answer
#2: Post edited by user avatar Monica Cellio‭ · 2021-10-24T19:25:08Z (12 months ago)
  • Bug/feature request.
  • When you click on a notification about someone responding to you with a comment, it takes you to the separate "comment page". Which is super confusing as it just drops you there without any context. What are they saying, what is this about?
  • In order to respond, I have to:
  • - Click on the link on top of the "comment page" to read the actual post.
  • - Expand the threaded comments under the post to read them in the same window. Including, figuring out _which_ thread the reply is found under, in case you've forgotten it by now.
  • - Open up a the "comment page" yet again in order to type a response. During which you won't see the post the comment is about.
  • ---
  • A temporary work-around to this particular bug could be:
  • - Upon responding to a notification, take the user to the _post_ being discussed. The post being the most important part.
  • - Auto-expand the comment thread where the comment that caused the notification can be found.
  • <span class="badge is-tag is-red is-outlined">status-completed</span> a different way: thread page now has expanders for the post and, if it's an answer, also the question. This provides the missing context without having to go through the extra hassle described here.
  • ----
  • Bug/feature request.
  • When you click on a notification about someone responding to you with a comment, it takes you to the separate "comment page". Which is super confusing as it just drops you there without any context. What are they saying, what is this about?
  • In order to respond, I have to:
  • - Click on the link on top of the "comment page" to read the actual post.
  • - Expand the threaded comments under the post to read them in the same window. Including, figuring out _which_ thread the reply is found under, in case you've forgotten it by now.
  • - Open up a the "comment page" yet again in order to type a response. During which you won't see the post the comment is about.
  • ---
  • A temporary work-around to this particular bug could be:
  • - Upon responding to a notification, take the user to the _post_ being discussed. The post being the most important part.
  • - Auto-expand the comment thread where the comment that caused the notification can be found.
#1: Initial revision by user avatar Lundin‭ · 2021-07-01T11:25:49Z (over 1 year ago)
Bug/feature request.

When you click on a notification about someone responding to you with a comment, it takes you to the separate "comment page". Which is super confusing as it just drops you there without any context. What are they saying, what is this about?

In order to respond, I have to:

- Click on the link on top of the "comment page" to read the actual post.
- Expand the threaded comments under the post to read them in the same window. Including, figuring out _which_ thread the reply is found under, in case you've forgotten it by now.
- Open up a the "comment page" yet again in order to type a response. During which you won't see the post the comment is about.

---

A temporary work-around to this particular bug could be:

- Upon responding to a notification, take the user to the _post_ being discussed. The post being the most important part.
- Auto-expand the comment thread where the comment that caused the notification can be found.