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
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...
Answer
#1: Initial revision
by
Monica Cellio
·
2023-02-27T15:10:07Z (almost 2 years ago)
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.