Closed Bug 35244 Opened 26 years ago Closed 26 years ago

Changing location of a frame

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Windows 2000
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: bugzilla, Assigned: nisheeth_mozilla)

References

()

Details

(Whiteboard: [nsbeta2+] Dependent on bug 37463)

I've been using a javascript URL to change the contents of two frames at one time: <script> function changePages(navbarURL, contentURL) { parent.content.location.href=contentURL; parent.nav.location.href=navbarURL; } </script> What happens under the preview release of Netscape 6 is that one frame get loaded into _top. Check the URL to and click on Products in the sidebar to see it happen.
-->DOM0 (dup 31378? but this seems to lock up whenever I tried, 4/10 debug build, NT)
Assignee: rogerl → jst
Status: UNCONFIRMED → NEW
Component: Javascript Engine → DOM Level 0
Ever confirmed: true
QA Contact: pschwartau → desale
Status: NEW → ASSIGNED
Target Milestone: --- → M18
Nominating nsbeta2. We have to start drawing a line on DOM0 backward compatibility; these bugs are supposed to be a high priority for nsbeta2 per the beta2 criteria.
Keywords: nsbeta2
This is needed for beta2, given the "lockup"; giving PDT approval.
Whiteboard: [nsbeta2+]
Seems there are a few problems here, the first problem is that the url is to a frameset with frames named "content", this problem is coverd by bug 33650. The other problem is the lockup, this is probably related to bug 36745 which has a partial fix attached, but the rest of bug 36745 is blocked by 31818. Waiting for the other bugs to be resolved before I'll look at this some more.
Depends on: 33650
Taking this from jst as discussed in the XML/DOM bug distribution meeting...
Assignee: jst → nisheeth
Status: ASSIGNED → NEW
Both bug 33650 and bug 36745 have been fixed. I will check with tomorrow morning's builds and see if this problem still exists. I tried this with a build from before the fix to 33650 landed and even that does not show any problems when I go to http://www.nestegg.com.au. Peter, it would be great if you can verify this bug on your end with the latest mozilla nightly builds also and report your findings on this bug. Thanks!
Status: NEW → ASSIGNED
Updating status whiteboard...
Whiteboard: [nsbeta2+] → [nsbeta2+] Needs testing...
Adding Johnny to the cc list...
I believe the problem with frames named "content" was solved yesterday, mozillas window.content was renamed to window._content. The lockup is most likely due to bug 37463 which even has a fix that should be checked in any day now... IOW once bug 37463 is fixed we should be able to close this one.
I checked with build Gecko/20000621 and it just locked up. I had to kill Mozilla with the task manager. Rest of the site worked fine. Clicking on one of the javascript links locked it up everytime. I was under Win2K at the time. I'll try again tomorrow night using the Linux build of Gecko/20000621
OS: Windows 98 → Windows 2000
Adding dependency to 37463...
Depends on: 37463
Whiteboard: [nsbeta2+] Needs testing... → [nsbeta2+] Dependent on bug 37463
This is fixed in the latest builds. Marking worksforme...
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Verified with 2000-07-05-09.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.