Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I'm a pretty active user in . I have been an active user for about 8 months now and I'm having a problem with a particular type of duplicate question.

The question has to do with why event handlers don't fire, or why widgets invoked on selected elements don't work on content loaded via AJAX or appended dynamically in some other fashion. There are so many duplicates of this exact problem:

The list goes on and on and on. It's even hard to search for questions like these because the problems sometimes involve particular events, functions being called, etc., etc.

I would love to start closing these as duplicates.

However, I can't find a solid, well worded question and answer that I can link to when I would like to close it as a duplicate (please let me know if you find one that does).

At first as a new user I welcomed these problems ("OH I know that! Easy rep!"), but now I believe that posts like these are just cluttering the tag up.

I thought of two options:

  1. Write a question and answer it myself (or let the community answer it) just for the purposes of getting a decent question that encompasses issues of this type so that we can redirect people to it and start closing these types of questions.
  2. Add an entry in the tag wiki. This is probably a good idea, but how many casual/new users are actually perusing the tag wiki?

I'm sure this isn't the only situation in which a question manifests itself in different ways. What's the best way to deal with duplicates of this nature?

share|improve this question
Improve an existing question, post a canonical answer, and close all others as duplicates of that one. Same deal as I suggested here. Hard to see what the problem is. – Cody Gray Jul 16 '11 at 7:39
up vote 4 down vote accepted

#1 is the best solution. However, make sure that even the initial answer is fairly comprehensive, and aim for a broad and comprehensive but detailed answer.

share|improve this answer
Thanks. I figured this was the correct way to do this. – Andrew Whitaker Jul 18 '11 at 16:05

I recommend #1, that you create a question and answer it yourself. But I would make it community wiki so users don't eye your reputation and assume you're trying to cash in on the easy reputation and badges made by basic questions. And, of course, it would be more honest given your intention.

share|improve this answer
I disagree with this. If you spend time composing a question or answer that others in the community find helpful and choose to upvote, then you deserve all the reputation you get from those upvotes. – Cody Gray Jul 16 '11 at 7:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .