* Roberto A. Foglietta <roberto.foglietta@sad.it> wrote:
As for meta-refresh, I suppose it could be included without causing much trouble, on two conditions: It should retain its current "warn the user instead of refreshing" behavior, if the refresh goes to a different page. Also, it should let the user specify a minimum refresh time that the page cannot override. This would allow it to follow W3C standards, and not bother users.
Since the first patch I published the refresh meta tag has to be activated by '-r' option or it doesn't work and show the warning as usual. If you use the '-r' option so dillo behave like every bloat mozilla/firefox/opera/ie etc. etc.
The option could *not* be save in the /etc/.dillorc but has to be put on the command line. Scott, do you thing this is sufficent? An option have to be activated by the user so I suppose he/she has to know what that option will be. If I want to be bothered, may I choose it? ;-)
It seems to me like something which should be in the config file instead of the command line. I also don't think it should follow refresh links to other pages; it's annoying and the W3C recommends not doing so. A single config option could work; something like "min_refresh_time=5" would enable the feature, and prevent it from reloading more than once every 5 seconds. Or, set the value to -1 to disable the feature and revert to previous behavior. As a command-line option, I'd probably never use it. I don't want dillo to refresh automatically to a different page, ever, so I wouldn't turn the feature on most of the time. But I don't usually know in advance when I'll view a page which refreshes itself, so the feature wouldn't be enabled when I want it. I'm just a regular dillo user, though, so I don't get to decide which patches are accepted. :) -- Scott