Mozilla and Google's prefetching functions are a nice addition to browser technology in many ways. Unsurprisingly, they are not very well thought through. The main two problems with the prefetching idea are that it messes with log files and it means every link on a page could potentially be followed despite the consequences (dangerous in a site administration context).
It appears from the FAQ that Google only intends their accelerator to prefetch specific pages, that have been specified with the <link> tag. However, many people are claiming that normal links have been prefetched.
To prevent prefetching of a page is simple: add the following PHP to the page you do not want prefetched:
if ((isset($_SERVER['HTTP_X_MOZ'])) && ($_SERVER['HTTP_X_MOZ'] == 'prefetch')) {// This is a prefetch request. Block it.header('HTTP/1.0 403 Forbidden');echo '403: Forbidden<br><br>Prefetching not allowed here.';die();}
This will serve a "forbidden" header to the prefetcher. Normal browsing should be unaffected.
AddedBytes.com is the online playground of 
I have to wonder why Javascript is used in favor of an intermediary confirmation screen that requires a POST request to complete the delete action?
Off the top of my head I can think of one big one: intercepting a GET request with Javascript saves the user (and the server) an additional page load.
XMLHttpRequest is perhaps an option, but is it yet viable?