Bug 19852 - "abort" algorithm being called from the navigate algorithm causes salvagable=false always
Summary: "abort" algorithm being called from the navigate algorithm causes salvagable=...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Depends on:
Reported: 2012-11-04 11:38 UTC by Silvia Pfeiffer
Modified: 2012-11-11 01:07 UTC (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Silvia Pfeiffer 2012-11-04 11:38:49 UTC
+++ This bug was initially created as a clone of Bug #18413 +++

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.

Staged to adopt:
Comment 1 Silvia Pfeiffer 2012-11-11 01:07:43 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
you are satisfied with this response, please change the state of
this bug to CLOSED. If you have additional information and would
like the Editor to reconsider, please reopen this bug. If you would
like to escalate the issue to the full HTML Working Group, please
add the TrackerRequest keyword to this bug, and suggest title and
text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this
document:   http://dev.w3.org/html5/decision-policy/decision-policy-v2.html

Status: Accepted
Change Description:
Rationale: adopted WHATWG change