The problem was, the question was already fairly general: unlike many similar questions on SO, it didn't specify a server or server-side language, or a laundry-list of application-specific requirements; even jQuery turned out to be more or less optional, leaving "no Flash" as the only real restriction...
In this case, you'd have been better served hunting down a previous question with the same restriction (no Flash) that did list an additional, superfluous requirement (say, PHP) which didn't figure into the answers and generalizing that... And then voting to close the new one as a duplicate. This was sorta the point of the blog post - users don't necessarily know what details are relevant until after their question has been answered... But once that's happened, you (the editor) can go back and remove the red herrings, allowing others to more easily benefit from it.
...Oh... And to answer your title question: no, don't fight. Edit wars are pointless. Don't ever be afraid to edit aggressively, but always respect the original author's right to reject your changes. If you feel the OP (or anyone else) is actively hurting a question by rejecting your edits, then flag for moderator attention or post about it here.