I believe they're doing a meta-tag redirect (possibly inside a noscript tag?) in at least some cases. Source: I'm developing a web engine that doesn't have JS support.
<!DOCTYPE html>
<html>
<head><title>Google Search</title>...</head>
<body>
<noscript>
<meta content="0;url=/httpservice/retry/enablejs?sei=..." http-equiv="refresh">
<div style="display:block">Please click <a href="/httpservice/retry/enablejs?sei=...">here</a> if you are not redirected within a few seconds.</div>
</noscript>...
<noscript><meta content="0;url=/httpservice/retry/enablejs?sei=a3qIZ42cGcvcp84P5p_mwQI" http-equiv="refresh"><style>table,div,span,p{display:none}</style><div style="display:block">Please click <a href="/httpservice/retry/enablejs?sei=a3qIZ42cGcvcp84P5p_mwQI">here</a> if you are not redirected within a few seconds.</div></noscript></header>
That depends. It works on setups where google still gives you the old html results but not one setups where it sends you to the js application. So on 3 out of 5 of my desktop setups it works. On the ones where, for some reason, google only sends me to the JS app, it doesn't work like you suggest, or, it does, but I'm just left looking at a blank page.