This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18119 - The exact effect of cancelling a navigation doesn't seem to be well defined. This should be defined and we should be clear on e.g. whether this prevents the load event firing, what happens to readyState, etc.
Summary: The exact effect of cancelling a navigation doesn't seem to be well defined. ...
Status: RESOLVED DUPLICATE of bug 18291
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:20 UTC by contributor
Modified: 2012-09-14 09:48 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2012-07-18 17:20:37 UTC 
This was was cloned from bug 16772 as part of operation convergence.
Originally filed: 2012-04-18 10:33:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-04-18 10:33:47 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#dom-window-stop
Complete: http://www.whatwg.org/c#dom-window-stop

Comment:
The exact effect of cancelling a navigation doesn't seem to be well defined.
This should be defined and we should be clear on e.g. whether this prevents
the load event firing, what happens to readyState, etc.

Posted from: 2001:4c28:a030:30:219:99ff:fe0e:5501
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.10.282 Version/12.00
================================================================================
Comment 1 Robin Berjon 2012-09-14 09:48:12 UTC 

*** This bug has been marked as a duplicate of bug 18291 ***