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.
Misleading button wording "Return to post"
Main suggested change
In a suggested edit page there is a “Return to post” button at the top right.
This only makes sense when the previous page was the post. When the previous page was the list of suggested edits it does not make sense to say "Return". It would make more sense for the button wording to be “View post”.
Optional extra change
Sometimes the user may wish to return to the list of suggested edits. Rather than using the word “Return” and trying to change the wording based on where the user came from, we could simply have two buttons, one to view the list of suggested edits and one to view the post.
This might be worth splitting into two separate changes:
- Change "Return to post" to "View post" so it doesn't look out of place when the previous page was not the post.
- Add a "View suggested edits" button for when someone views a suggested edit and then decides they want to skip it and view the list again instead.
I suggest splitting these because part 1 is a trivial wording change, whereas part 2 requires knowing which category the suggested edit is in, which is non-trivial since the suggested edit page is not in a category, even though the suggested edits list page is. For this reason part 2 might be deferred as future work or possibly omitted altogether. Having a link to the post seems useful, but someone working through suggested edits can easily use their browser back button to return to the suggested edits list.
1 answer
Request #1 is now live; the button says "view post", implying nothing about how you got there.
We have some discussion in progress about how to approach request #2. If the suggested-edit page were "in" its category, you'd see the edits link right there. So that's one possibility, but we need to investigate what's practical from a code perspective.
1 comment thread