On Thu, 22 Aug 2013, Andrew Oakley wrote:
On 19/09/12 01:18, Ian Hickson wrote:
I've changed the spec so that traversing the history by a delta always
cancels any pending navigations unless you're in the middle of an
unload, in which case it just aborts the algorithm entirely.
I've
On 19/09/12 01:18, Ian Hickson wrote:
I've changed the spec so that traversing the history by a delta
always cancels any pending navigations unless you're in the middle of
an unload, in which case it just aborts the algorithm entirely.
I've also made back()/forward()/go() not work during the
On Tue, 12 Jun 2012, James Graham wrote:
In particular, what stops such navigations from re-triggering the unload
handler, and thus starting yet another navigation?
I've updated the spec to have guards in place for 'pagehide' and 'unload'.
(Not yet 'beforeunload'. Should we do that too?)
This is all great; thanks for the quick turnaround!
I've also made back()/forward()/go() not work during the document's unload
handler, since that could be used for griefing. I'm tempted to disable it
entirely for all docs a la alert(), but I've no idea if that's Web-
compatible and I suspect
On Tue, 18 Sep 2012, Justin Lebar wrote:
This is all great; thanks for the quick turnaround!
I've also made back()/forward()/go() not work during the document's
unload handler, since that could be used for griefing. I'm tempted to
disable it entirely for all docs a la alert(), but I've
I've also made back()/forward()/go() not work during the document's
unload handler, since that could be used for griefing. I'm tempted to
disable it entirely for all docs a la alert(), but I've no idea if
that's Web- compatible and I suspect not.
I don't know what you mean by the last
On Tue, 18 Sep 2012, Justin Lebar wrote:
The issue isn't a history.back() which crosses origins -- that seems
fine -- but rather calling history.back() on a cross-origin window.
(Sorry that wasn't clear.)
Aah, ok. The spec already says that's not allowed. You can't get to the
History
