Closed Bug 50980 Opened 25 years ago Closed 25 years ago

Going back in frames doesn't work correctly

Categories

(Core :: DOM: Navigation, defect, P4)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: mikepinkerton, Assigned: radha)

References

()

Details

(Whiteboard: [nsbeta3+])

- go to http://www.krispykreme.com/krispykr.html - click on one of the doughnuts on the left to load a new page in the big frame on the right - click back Expected: - you go back to the starting page in the right frame Actual: - nothing happens
this is probably a session history bug, feel free to reassign.
Keywords: 4xp, correctness, nsbeta3
I can't reproduce this bug exactly as reported. However, I do see a closely related problem. In today's NT build (pulled this afternoon), I see: - go to http://www.krispykreme.com/krispykr.html - click on one of the doughnuts on the left to load a new page in the big frame on the right - click back (we go back to the homepage here as expected - first time only) - click on one of the doughnuts on the left to load a new page in the big frame on the right (second time) - click back Expected: - you go back to the starting page in the right frame Actual: - we go back two pages to the one before http://www.krispykreme.com/krispykr.html in history Handing this off to session history
Assignee: pollmann → radha
Component: HTMLFrames → History
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Nav triage team: [nsbeta3+]. We could live with it going back "too far," as Eric describes, but the behavior we observed when testing ("we" often test this web site) is along the line of this bug's description.
Priority: P3 → P4
Whiteboard: [nsbeta3+]
QA Contact: petersen → claudius
This is fixed with the patches mscott checked in last week.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
VERIFIED Fixed with 2000091308 builds.
Status: RESOLVED → VERIFIED
Blocks: 59387
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.