Question: I sometimes ask questions for which the answer is ["this is not possible"](https://meta.stackoverflow.com/questions/261168/is-this-is-not-possible-an-acceptable-answer). One common source of these (and I suspect this happens to other question askers as well) is the relative lack of power of certain tools, such as CSS or regex. CSS can accomplish a lot of things, but it can't accomplish everything. So, questions asking "How can I accomplish X using CSS" sometimes have a "not possible" answer.

However, things that aren't possible in CSS are usually possible with JavaScript. This tends to elicit answers that "this isn't possible in CSS, but it *can* be accomplished in JavaScript. See here:...". [e.g.](https://stackoverflow.com/questions/71993071/how-can-i-scale-all-images-to-the-same-dimensional-area/72003152#72003152) (Note that in this question, @isherwood seems to have made a post hoc edit to the question to attempt to make the question accommodate his answer of "not possible... but". IMHO making the question more vague doesn't help clarify though - it hides the aspect of "trying to accomplish this in CSS" which obviates the useful "not possible" answer.)

I now have a question about CSS with a JavaScript answer. It seems that this answer actually answers *two* questions:

1. "Q: How to do this in CSS, A: Not possible" and
2. "Q: How to do this in JS, A: here's how...".

However, I can't edit my post so that it actually asks both of those questions; posts asking multiple questions get closed as **Needs More Focus**.

Does anyone have recommendations on general strategies to edit such questions post hoc or to a priori phrase questions that I suspect might be "not possible...but" so that they can accommodate both the original answer ("not possible", which is useful info to anyone looking to accomplish this) and *also* the new answer (the workaround) to the question I didn't ask?

Answer: 
Are you aware of [the XY problem](https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem)?

If you know that there are other technologies which might solve the problem, it would be useful to either say you'd accept answers using them *or* give a brief reason why you can't use them (but don't be upset if people don't accept the reason).

Also, remember that the Stack Exchange sites are intended to be a repository of knowledge for everyone, so someone else with the same problem may be happy to find an answer which uses, say, jQuery, even if that particular answer was of no use to you. (The "[Wisdom of the Ancients](https://xkcd.com/979/)" XKCD cartoon is so nearly applicable here.)
As with many things in life: **it is a judgement call.**

When deciding whether to widen the scope of a question based on answers, always ask yourself if value will be lost were the answer to be removed? Some answers, even if they broaden the scope of the question are stellar: detailed, properly formatted, well-written, etc. They provide value, so it makes sense to tweak the question a little to make an allowance for it (that said, if the question *explicitly* states that solutions in other technologies are *unacceptable,* I would avoid making such an edit as we generally strive to [preserve authorial intent](https://meta.stackoverflow.com/a/303220/11407695)).

If answer does not provide great value, try to find a common duplicate target that explains how to solve the problem in the technology of the answer, and if so, then the answer is actually *harming* the repository of knowledge such as we are because every user landing on it is one user that seen the canonical *less.* I do not propose outright *deletion* of such answers, but they certainly do not merit widening the scope of the question.

---

An off-note about your example post: it seems that you misunderstood the nature of the edit — the user was simply [removing tag duplication from title](https://stackoverflow.com/help/tagging) as the question is already tagged [css](https://stackoverflow.com/questions/tagged/css "show questions tagged 'css'") (the original title started with "css how").