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 18413 - "abort" algorithm being called from the navigate algorithm causes salvagable=false always
Summary: "abort" algorithm being called from the navigate algorithm causes salvagable=...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-26 16:12 UTC by James Graham
Modified: 2012-10-29 23:59 UTC (History)
3 users (show)

See Also:

Attachments

Description James Graham 2012-07-26 16:12:01 UTC 
Since "abort" is now called from step 11 of navigate, all documents get a salvageable state of false. Clearly the salvagable state should only be set to false when the previous steps actually had an effect.
Comment 1 contributor 2012-10-29 23:59:00 UTC 
Checked in as WHATWG revision r7488.
Check-in comment: Abort was a little over-enthusiastic.
http://html5.org/tools/web-apps-tracker?from=7487&to=7488