If page is still being loaded in another frame, subsequent clicks don't register in history

RESOLVED EXPIRED

Status

()

Core
Document Navigation
RESOLVED EXPIRED
16 years ago
10 years ago

People

(Reporter: Sean Jorden, Assigned: Radha on family leave (not reading bugmail))

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910

In a multi-frame setting, if one of the frames is still loading, then navigating
other frames does not seem to add pages to the session history.

This site uses one of the available HTTP 1.1 connections (we get up to 2, I
think) for push purposes, so one of the frames is always loading.

I *think* this may be cause of some other mysterious frame navigation bugs??
especially if some normal sites have frames that take a long time to load, or hang?

Reproducible: Always

Steps to Reproduce:
1. login to http://www.solve360.com
2. login with the the following credentials:
organization: noradatest
username: test1
password: test1
3. login and start navigating.. then press the back arrow. You are taken to the
front page.
4. now, login with the following information. This user has the conferencing
feature disabled, so the continuously loading frame will not be there.
organization: junglemate@promotion
username: junglematedemo8326
password: fordemouseonly
5. login and navigate around, the back arrow works properly.
Actual Results:  
back button goes to front page (ie individual frame navigation doesn't get put
in history)

Expected Results:  
recorded the frame navigation history regardless if another frame was being loaded.

Comment 1

14 years ago
Reporter: Is this still a problem with a current Mozilla build?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED

Updated

10 years ago
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.