Tavern on the Meta

12:13 AM

I feel a bit bad for suggesting to a new user to post a question, as the question is being downvoted...

4:16 AM

Should a feature-request which was implemented later as part of a general update be closed as a dupe or answered with a note that it is now status-completed?

I thought I knew the answer but I'm doubting myself...

Rob

4:45 AM

@bobble Search for the text "Should I answer ...":

266

Q: How should duplicate questions be handled?

What should I do when I see a question that is a duplicate of another one? Should I answer it? Should I downvote it? Should I comment? Should I edit the question to indicate it's a duplicate? If I can, should I (vote to) close the question? What happens when I vote to close as duplicate? Or: Wh...

bobble

@Rob I was unsure if it would count as a dupe

Is asking "please implement X bit of formatting" a dupe of a post that says "We've implemented a bunch of formatting updates"?

Rob

Seems that way, more of a guess at edge cases without a link to the question. Edit the FAQ to include the necessary information to answer your question, or ask a new question.

Back in a bit.

bobble

Specific questions: meta.stackexchange.com/questions/337979/… meta.stackexchange.com/questions/353446/new-post-formatting

Sonic the Anonymous Hedgehog

@bobble If it's specifically mentioned there, close as dupe. If not (e.g. it ended up becoming a non-issue due to another change and your feature change isn't specifically mentioned), do the latter.

bobble

> Refinements for revealing spoilers. We now reveal this on click / tap for a more consistent experience across devices—fewer accidental reveals as well, since it’s no longer a :hover interaction. Clicking again does not hide the spoiler. We also now add a badge to the top right corner. You can see how these work on our design system documentation. It looks something like this:

does it specifically mention keeping spoilers distinct from blockquotes once clicked? Honest question, since it definitely gets close

Meta Andrew T.

5:13 AM

I think the current grey background for spoiler blocks is now... permanent? Looks dupe to me.

Yeah, the announcement ammended it with "I’ve made sure to continue highlighting spoilers in gray."

but the answer was posted later? huh?

oh, countered by this answer, so, yes, it's a dupe now.

Rob

5:49 AM

@bobble I don't see a duplicate because the issue hasn't been fixed, nor is this a duplicates. I checked all the answers in your second link, and there's no mention of it, the first link was asked long before asked Aug 25 '20 at 17:41 (the time of the second link's announcement); the first link should have been marked a dupe sooner. Now the first link is an old request, and too long after the announcement; it might be bumpable (with a

necessary edit), but that won't help it much. This is what I see using.my browser:

Notice under "Draft saved" the bold vs non-bold.

It just hit the review queue, and I reviewed it consistent with the above.

Rob

6:25 AM

@bobble I stand corrected, MAT's link is correct; sorry it took so long to answer, in the middle of something. Changing review.

The part about the boldness still stands for Mobile FF and Chrome; left a comment.

Transcript for