Closed Bug 331835 Opened 19 years ago Closed 17 years ago

unfinished xmlhttprequest prevents fastback

Categories

(Core :: DOM: Navigation, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: hax.sfo, Unassigned)

Details

(Keywords: testcase)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 if the user forward to next page, while there is an unfinished async xmlhttprequest, fastback feature will be disabled... is this behavior by design? I also notice that readyState of that request will become to 3 and 4 (which skip 2) before pagehide event (and after onbeforeunload if exists), so that i have no easy way to abort that request in the pagehide handler to make fastback work... And even worse, the typical codes of onreadystatechange which access req.status will throw an Exception! Reproducible: Always
Attached file testcase
NOTE: 1. require a dummy page named next.html 2. require a server page named /sandbox/sleep which will sleep some time.
Attached file testcase
(In reply to comment #0) > if the user forward to next page, while there is an unfinished async > xmlhttprequest, fastback feature will be disabled... is this behavior by > design? Related to bug 274784 comment 49?
Keywords: testcase
Yes, this is by design. When you leave a page we abort all network activity (as in most cases you want to free up bandwidth and connections for the new page). This means that it is impossible to restore the state that the page was left in.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: