Lol, you guys are nuts. Robin uses tech that processes your post though Ajax (or equivalent), so it doesn't have to make a full page request. Sometimes, the return data on those gets sploogified, or the script engine never handles it properly.

The reason the post gets through is because the server got the request and processed it, but your browser either never received or failed processing the return data.

I personally recommend you use Chrome as your browser of choice. Install the AdBlock plugin for sure, and sync it across your google account. That gives me access to all my bookmarks, history, settings, etc... Across all of my devices that use Chrome (home laptop, work laptop, work desktop, iPad, s3cell, etc...).

Of course it can happen on all three... It's most likely to be a dropped packet or a server that never sent anything. Sploogified is my fancy term for "lost in the ether".

That's when most people's code will wait forever for the return (why you see the spinning circle forever, even though the post has been made).

The two paragraphs were meant to be de-coupled, I probably could have written it better. I didn't blame a specific browser, but I am definitely recommending chrome for all the reasons I listed. That was done in response to some people saying they use Firefox.

It's not the browser, its the javascript that's being run.

A suggestion might be for Robin to include code that kicks off a timer, and asynchronously checks for the status of the post, instead of waiting on an ajax return.

I should add that I have not ever looked at Robin's code, so I may be completely misstating how he has his tech set up, but the general concept of what I am telling you holds true.

I agree...........