W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2015

[whatwg] Page refresh interface

From: Andrea Rendine <master.skywalker.88@gmail.com>
Date: Tue, 24 Mar 2015 02:41:30 +0100
Message-ID: <CAGxST9=9s5xStJoM-y8NSjprVT38DG5isP_WZNR4Z+Y5ePwuEA@mail.gmail.com>
To: WHATWG List <whatwg@whatwg.org>
Hi everybody!
A request starting from <meta> element and its refresh state: why doesn't
the document interface expose the refresh timeout? The ideal would be to
expose it in read/write mode, as authors have evolved several variants of
location.href/replace/refresh/reload. And for "several" I mean 534:
http://www.phpied.com/files/location-location/location-location.html .
Having a writable property would allow e.g. to delay the refresh or even to
stop the pragma "refresh" instruction and replace it with a timed AJAX
recall of specifi contents, maintaining a nonscript whole-page refresh for
cases where scripts are disabled/unavailable.
But even without a writable property, it would be useful to just have
"read"-level properties such as document.refreshTime and
document.refreshUrl . Consider that refresh time (along with a refresh URI)
can be set by (non-standard (why non-standard?)) header response, a <meta>
element already present (and there can be more than one, as UAs know how to
handle this error) or even being inserted at runtime. So it is difficult to
access this information without a proper interface.

Besides that, the spec says that UAs may expose the time (and other
aspects) for a refresh event of the document and it also refers to the
possibility for a user to "cancel the redirect", while as of now users
aren't even informed, let alone allowed to interact with this event.
Received on Tuesday, 24 March 2015 01:41:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:29 UTC