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
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
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.

No response when clicking on the title of a thread on a recently deleted post

+1
−0

When clicking on the thread title ("Welcome!" in this example) of a comment thread below a post:

Comment thread title in context

I see the following error in the Firefox developer window (click image for a larger version):

Errors from developer window

The reason is that the post has been deleted since I opened the page, so I am no longer permitted to view it (including any comment threads on it). However, this is not communicated to the user. Without the developer window, there is no indication that anything is wrong - clicking on the thread title has no effect.

What should be the behaviour in this case? Should a message be displayed indicating that comments cannot be retrieved because the parent post has been deleted? Should the page redirect to the 404 page that would be displayed if the user had tried to view the parent post?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+1
−0

I think we should match "interaction type". The person clicking on a thread title expects an in-page expansion, not a new page, so I think an in-page notification about the deletion is better than moving to a separate 404 page.

When the front-end code finds out about the deletion (by trying to expand the thread and failing), I think it would be a nice bonus to also add the deletion styling (pink background) to the post, as a reminder. Yes, you (probably) wouldn't be able to see that post on a fresh load, but if you're already there and thus able to see it, let's mark it as deleted on the client side. When you navigate away, you won't be able to come back.

Why not just kick you out with a 404 as soon as the deletion is known? Expanding a comment thread, which you might do while still reading the post if you notice a related title, seems like an odd trigger to have a post disappear right out from under you. I think it's better to let you keep reading what's already in your browser, without opening up more deleted content like comment threads, and communicate clearly about the state.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »