Closed Bug 79953 Opened 23 years ago Closed 23 years ago

document unnecessarily reloaded when jumping to an anchor

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: mkes, Assigned: karnaze)

References

()

Details

Attachments

(1 file)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9) Gecko/20010505
BuildID:    2001050515

Let's say I have a HTML document which uses 2 frames. The document itself is a
local file (file:// ... ) as well as documents displayed in each frame. Let's
say the left frame displays a document that contains list of links (e.g. index)
to the document displayed in the right frame. It looks like the browser reloads
the whole document in the right frame each time a link in the left frame is
clicked. If the document in the right frame is big enough the reload takes time
and it looks like strange behavior of the browser because first the beginnig of
the document is displayed and after the document is completely loaded the
browser scrolls to the corresponding part of the document.

Reproducible: Always
Steps to Reproduce:
I think it is clear from the description.



Actual Results:  See the description.

Expected Results:  Browser should check that the document is already loaded in
the frame and just jump to the corresponding anchor without reloading it again.
updating component
Assignee: asa → karnaze
Component: Browser-General → Layout
QA Contact: doronr → petersen
Changing QA contact to amar
Component: Layout → HTMLFrames
QA Contact: petersen → amar
Reporter, can you attach a testcase?
I've also put the testcase up at 
http://pyrallis.aegisknight.org/79953testcase/kb_v101.html.  Using IE5.5 and 
today's commercial build (2001052904) on Win2K, I don't see the problem.  Here 
are the relevant Apache logs:

Internet Explorer 5.5:

h-208-12-38-212.netscape.com - - [29/May/2001:14:04:32 -0800] "GET 
/79953testcase/kb_v101.html HTTP/1.1" 200 333 "-" "Mozilla/4.0 (compatible; MSIE 
5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:04:32 -0800] "GET 
/79953testcase/kb_v101_index.html HTTP/1.1" 200 8439 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101.html" "Mozilla/4.0 
(compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:04:32 -0800] "GET 
/79953testcase/info.gif HTTP/1.1" 200 130 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:04:32 -0800] "GET 
/79953testcase/must.gif HTTP/1.1" 200 86 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:04:32 -0800] "GET 
/79953testcase/may.gif HTTP/1.1" 200 86 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:04:44 -0800] "GET 
/79953testcase/kb_v101_content.html HTTP/1.1" 200 549677 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101.html" "Mozilla/4.0 
(compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:05:21 -0800] "GET 
/79953testcase/kb_v101_content.html HTTP/1.1" 304 - 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_index.html" "Mozilla/4.0 
(compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:05:21 -0800] "GET 
/79953testcase/info.gif HTTP/1.1" 304 - 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:05:21 -0800] "GET 
/79953testcase/must.gif HTTP/1.1" 304 - 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
h-208-12-38-212.netscape.com - - [29/May/2001:14:05:21 -0800] "GET 
/79953testcase/may.gif HTTP/1.1" 304 - 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)"

NS6:

h-208-12-38-212.netscape.com - - [29/May/2001:14:18:43 -0800] "GET 
/79953testcase/kb_v101.html HTTP/1.1" 200 333 "-" "Mozilla/5.0 (Windows; U; 
Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 Netscape6/6.5b0"
h-208-12-38-212.netscape.com - - [29/May/2001:14:18:44 -0800] "GET 
/79953testcase/kb_v101_index.html HTTP/1.1" 200 8439 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101.html" "Mozilla/5.0 
(Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 Netscape6/6.5b0"
h-208-12-38-212.netscape.com - - [29/May/2001:14:18:44 -0800] "GET 
/79953testcase/must.gif HTTP/1.1" 200 86 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 
Netscape6/6.5b0"
h-208-12-38-212.netscape.com - - [29/May/2001:14:18:44 -0800] "GET 
/79953testcase/info.gif HTTP/1.1" 200 130 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 
Netscape6/6.5b0"
h-208-12-38-212.netscape.com - - [29/May/2001:14:18:45 -0800] "GET 
/79953testcase/may.gif HTTP/1.1" 200 86 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101_content.html" 
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 
Netscape6/6.5b0"
h-208-12-38-212.netscape.com - - [29/May/2001:14:18:55 -0800] "GET 
/79953testcase/kb_v101_content.html HTTP/1.1" 200 549677 
"http://pyrallis.aegisknight.org/79953testcase/kb_v101.html" "Mozilla/5.0 
(Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010529 Netscape6/6.5b0"

Ugh, sorry about the formatting.  I tried IE first.  I went to the page and 
clicked on one item on the left side.  In Mozilla, I did the same.  As you can 
see, IE asked the server for the files again, but the server sent back a 304 
(use local copy).  Mozilla did not ask the server.

I also tested the page locally, and to me, Mozilla would just jump directly to 
the part of the page in the second frame.

Can you still see the problem in recent builds?
From e-mail (in the future could you just post comments in the bug?  It makes
things a lot easier.  Thanks):

> Ugh, sorry about the formatting.  I tried IE first.  I went to the page and
> clicked on one item on the left side.  In Mozilla, I did the same.  As you can
> see, IE asked the server for the files again, but the server sent back a 304
> (use local copy).  Mozilla did not ask the server.

Yes, it the log listing looks like it doesn't ask the server again.

> I also tested the page locally, and to me, Mozilla would just jump directly to
> the part of the page in the second frame.

Not in my case. Now when you have the test case I can explain the
observations I have based my report on.
If I open the document the first item shown in the right frame is the "
Antialiasing filter mounted improperly".
Now if I click lets say item #21 ("Coupling backlash") in the left frame
...

... IE jumps to the corresponding item in the right frame immediately


... Mozilla first clears the right frame, then it displays the top of the
whole document ("Antialiasing filter mounted improperly") and after some
delay jumps to the requested part of the document. If I look at the
scrollbar of the right frame during that "delay" the "slider button" (I
don't know what is the correct term in english) is first positioned at the
top of the scrollbar and it is getting smaller and smaller (as the document
is being loaded) and after the whole document is loaded its position
changes somewhere to the middle of the scrollbar (as it corresponds to the
position of the requested anchor within the whole document).

This is how it appears on my machine (PIII 800MHz 256MB RAM and SCSI
harddrives - not too slow).


> Can you still see the problem in recent builds?


No. But I tried the FreeBSD version (the one which is on Mozilla's web site
as mozilla-i386-unknown-freebsdelf4.1-0.9.tar.gz) on the same machine toady
and the behavior is exactly the same.


Well, I looked at the test case with Mozilla 0.9, and I saw the behavior you
described.  However, I don't see it anymore in recent builds, so I'm marking
this WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
 Works fine on recent build ID : 2002012403
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: