Closed
Bug 28971
Opened 26 years ago
Closed 26 years ago
Framesets + Reloading does not work well
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
People
(Reporter: saschmit, Assigned: pollmann)
References
()
Details
Build ID: 2000022217
User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.12-20 i686; en-US)
Steps to reproduce:
1) Load the above url
2) Cycle through the various yellow links in the left frame menu (except the top
one, which merely switches between a full list of links and a shorter list - the
url above starts you with the full list)
3) You will note that some will eventually appear with black background and some
with gray. This is described in a separate (though possibly related) bug report
(bug 28643).
4) Go through several links (3 or 4 should do - avoid the off-site links near
the bottom).
5) Now reload the page.
Expected behavior:
- The page should stay the same, except, of course, reloaded.
Actual behavior:
A) it actually loads as you might expect, or
B) what *should* be in the right frame ends up in the left one OR the left frame
does not render at all (and suffers what appears to be painting problems when
overlapping windows)
If you do not observe the bug, reload again. This does not always show up
immediately. For me, I can always reproduce this bug given enough reloads.
Once what should be in the right frame appears in the left (the right will
contain the page that was shown when first loaded) use of the back button only
affects the left frame and goes back through all the pages you've visited, all
the way back to the original left frame. Once you are here, you can select links
and have them show up in the right frame as before.
The url given bug 28643 also exhibits the bug (and I suspect, nearly any
frameset), so use that if my site is unavailable or you want another test case.
Comment 2•26 years ago
|
||
I tried all the links several times, reloaded 10 times. I do see the background
change from black to gray (seperate bug). The problem with the back/forward
button is bug 28142. I do not see the other problems you described. So,
works-for-me on linux build 2000-3-3-12
| Assignee | ||
Comment 3•26 years ago
|
||
I cannot access the test site to confirm, please attach the pages to the bug
report, thanks!
| Assignee | ||
Comment 4•26 years ago
|
||
I was not able to reproduce this at your site (which I was able to access
tonight), but I was able to reproduce it a vidiot.com (on Win NT). I'll look
into this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
| Assignee | ||
Comment 5•26 years ago
|
||
Steps to reproduce:
Visit http://www.vidiot.com/TVShows.
Click on Ally McBeal link in left frame.
Wait for page to completely finish loading.
Click Reload button.
Ally frame will be reloaded into left frame.
I'm 99% sure this is a dup of bug 28142. Let's say you have two frames, Frame A
and Frame B. If you click on a link in Frame A that actually updates Frame B,
the session history entry for Frame A will then be updated to say "Visited Frame
B".
When you click reload, the session history is used to determine which URL's to
load in each frame. Since Frame A thinks it is showing the new page in Frame B,
it will load that page. I'm going to mark this a duplicate, and note that this
should be tested when that bug is fixed. Thanks for reporting this bug!
*** This bug has been marked as a duplicate of 28142 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Comment 6•26 years ago
|
||
I tried and cannot reproduce this bug on linux build 2000-3-3-16. I followed
the steps pollman described. Upon hitting reload, the pages reloaded in their
original frames. Bug 28142 is still present, I can get the pages to load in the
wrong frame by hitting the back button, but on reload the original layout comes
back.
Updated•8 years ago
|
Product: Core → Core Graveyard
Updated•8 years ago
|
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.
Description
•