If you are talking about another's computer then (re)write the cookie with
an expiration date set to 'now' or before.
The GMT date string representation of epoch appears to be the most reliable
and most easily computed invalid value to cause instantaneous non-HTTP-only
cookie deletion (it MUST be "GMT" per the cookie protocols – although recent
UAs appear to accept "GMT+0000 (UTC)" as well –, which means you SHOULD use
Date.prototype.toUTCString()).
Setting the expiration date to now is possible to only make the cookie a
session cookie, deleted not before the browser session ends (i.e., when all
browser windows are closed). Setting it to the string value 'now' has no
effect at all, of course. (But perhaps you meant something else. Also,
there is currently an error in the MDN documentation of document.cookie when
it says that you can delete a cookie by setting its expiration time to zero.
Instead, you need to set the time _value_, of Date instance that generates
the GMT date string representation used, to 0; i.e. you should use epoch,
AISB.)
This may be done with the same page or another from the same site. When
the page is closed or the browser closed, the cookie will vanish. (Of
course, how you get other people to reload such a page is a different
question and again must be done in each browser.)
Reloading the document is unnecessary to delete a cookie using *client-side*
scripting (which is what discussions in this newsgroup are about, unless
stated otherwise). Just assign an appropriate value to the document.cookie
property.
Please get yourself a real name.
PointedEars