Why not? As it seems, JS is not doing anything that isn't do-able with a <a href="...file..." target="_blank"> - as soon as the browser gets a file that it cant render (.zip, ...), it will download it.
The magic is in the server, which must set the MIME type to application\octet-stream or something similar, so the browser doesnt try to render certain browser-rendable files (.htmls, .pdfs, ...)
I just mean users without JS usually aren't ones who are downloading files. Lynx is possibly an exception, though, since it's sometimes used by server admins like myself to grab packages.
Ah ok. But is there some reason for Lynx not to support JS? Is this by design? I also found out about links [1] and elinks [2] but seems that their JS support is marginal or requires compiling with certain flags [3]. Haven't anyone tried to incorporate V8 yet?
Implementing JS would be a huge undertaking (they'd have to implement lots of APIs and the DOM, for starters). Such text-mode browsers are usually light on resources, too, and this would change that. Also, JS is usually used with the assumption graphics support is there.