> As I understand it, using Refresh 0 is bad, That's because it is used to simulate a redirect when there is a perfectly good way of doing this which is blessed by the standards and can let the browser know that it should update bookmarks (even if it doesn't). Refresh, although mentioned in the HTML specification is not specified there, and is, as far as I know, not specified in any other non-proprietory specification.
> but I suppose using 1 and above You are still abusing it for a redirect, and even when using it for its intended purpose of producing a slide show, in which case 1 second is too short (it's actually too short to allow some people to get past it with the back button). However, for anyone not fluent in a language or not reading visually, any auto-advance time delay suitable for fluent visual users is likely to be a problem. Lynx is often used by blind users without a rich employer to pay for JAWS. > instead of 0 isn't bad, so at least for those I would be happy if Lynx would > automatically redirect. Or is that a problem for some reason? > > The only thing I use it for is, if I want an easy way to tell a browser not to > use this or that static file, but instead some other file, that is very often a > dynamically generated file. And very often it is mostly because I like to start If you can generate dynamic content, you are almost certainly able to configure the server to generate proper redirects; there is a slight excuse for this abuse of Refresh for people with cheap web space where they cannot control meta data, but you can control meta data with dynamic content, so that restriction shouldn't apply. ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
