HTTP 204. You send the request, the browser stays where it is. Super simple, and...

jff · on Jan 21, 2016

The interesting thing about the modern web developer is that they don't know jack or shit about HTTP.

donatj · on Jan 21, 2016

Yes. Quite literally "kids these days". HTTP is so powerful and so under utilized today.

esailija · on Jan 21, 2016

Is there a spec that the browser must stay where it is? Otherwise I would just use a form targeted to a hidden iframe. Still it's not usable here since you won't see your vote or comment or anything without reloading the entire page.

donatj · on Jan 21, 2016

https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html "If the client is a user agent, it SHOULD NOT change its document view"

Also, a tiny bit of JS and no ajax can solve that easily.

esailija · on Jan 21, 2016

The spec language "SHOULD" is not same as "MUST" at all.

> Also, a tiny bit of JS and no ajax can solve that easily.

No disagreement from me that JS solves these issues.

icebraining · on Jan 21, 2016

The spec language "SHOULD" is not same as "MUST" at all.

No, but in practice all major browsers (Firefox, Chrome, IE, Opera and Safari) do so. And it's not like the implementations of JS and its APIs never differ.

eropple · on Jan 21, 2016

> The spec language "SHOULD" is not same as "MUST" at all.

There are edge case clients that would need to contravene this. Most of those clients don't support JavaScript (or in many cases video) in a meaningful way, making the whole thing moot.