Comment in question. http://www.videosift.com/video/Wrestling-with-Microsoft-Vista-Speech-Recognition

(Do these show up in log when the AJAX hits submit from client side? Or it doesn't even make it to server??)

we have noticed that apache is blocking some comment commands for instance anything with tar followed by a dash such as star dash where dash is actually a - has problems going through. It's on our list of bugs but is admittedly pretty low on the list.

I think everyone experiences that from time to time. From what I can tell, it's the JavaScript hanging for no apparent reason and is regardless of comment content, and sometimes the comment is posted, but other times not.

It isn't very nice to have to deal with, but is an unfortunate quirk that's near impossible to mitigate. If it happens again and you're on FireFox try opening the Tools > JavaScript Console and seeing if there are any errors reported. If so, copy and send it/them to me and I'll see if maybe there's a clue I can use to dream up a fix.

[edit]
Oh, yes. James points out something I forgot which can cause a hang and no-post, but is usually much more rare than just the unexplainable hanging I was talking about.

Your wish is my command...

(FireFox 2.0.0.1 / XP SP2)
Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: http://www.videosift.com/js/script.php?id=32964&login=&from=%2Fstory.php&fromuri=video%3DMy-TuneOr-Ploink :: anonymous :: line 361" data: no]


Unrelated, but on sucessful comment posts, I get these (just FYI):

Error: urchinTracker is not defined
Source File: http://www.videosift.com/talk/My-TuneOr-Ploink
Line: 526

Warning: Unknown property '_height'. Declaration dropped.
Source File: http://www.videosift.com/css/style.php
Line: 350

That actually helps. Thanks for the info, jd. I've implemented a change that will hopefully fix it. Let me know if it happens again, including the error message. (Make sure you've done a ctrl+f5 or shift+refresh beforehand, though, to insure you have the updated JS code.)