Closed Bug 41438 Opened 24 years ago Closed 24 years ago

window._content.location.href doesn't work well with SH

Categories

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

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: jelwell, Assigned: radha)

References

Details

(Whiteboard: [nsbeta3+])

This is probably the same as bug 29542, although this bug effects comm bits as
well, I assume.

Steps to reproduce:
1) load www.yahoo.com
2) click on the mozilla icon to load www.mozilla.org

notice your history now has two entries for www.mozilla.org, and the yahoo link
is gone from the history.

This can cause real headaches, much more so than tinderbox bug as it's more
accesible.
I'm currently using linux build 2000060320.
Yes, this is very similar to 29542, but not exactly. i know what the problem is. 
Shall fix, once the tree opens for M17.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
*** Bug 46499 has been marked as a duplicate of this bug. ***
Updating summary to reflect the real problem behind this bug and bug 46499 
(sorry to morph this a bit, but it's still really the same problem as 
originally reported).  See the whole reasoning in my comment at the end of 
46499.

Also see perhaps-related bug 42723.  cc'ing rick...
OS: Linux → All
Hardware: PC → All
Summary: Clicking mozilla icon clobbers current page in history. → window._content.location.href replaces last page in SH with new URL
I have a feeling 44660 and 29542 are related to or duplicates of this.

Also, I'm updating the summary a bit.   The behavior here seems erratic 
somewhat.  Sometimes window._content.location.href replaces the last item in 
SH, sometimes it simply deletes it, and sometimes it doesn't seem to affect SH 
at all (i.e. not added to it, but doesn't delete anything from it either).
Keywords: nsbeta3
Summary: window._content.location.href replaces last page in SH with new URL → window._content.location.href doesn't work well with SH
nav triage team:
gotta get session history working better
Whiteboard: [nsbeta3+]
window.content.location.href is integrated with SH now. Please try again. 
Originally any url visited thro' window.content.. was not getting in to SH. Now 
it does.
so your sayingthis is fixed? Okay, marking fixed and I'll check it out when I start verifying nsbeta3+ bugs (Really Soon Now)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
VERIFIED Fixed with 2000082308 builds
Status: RESOLVED → VERIFIED
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.