Closed
Bug 129474
Opened 24 years ago
Closed 24 years ago
resizing a frame causes script objects to be lost
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: fred, Assigned: jst)
References
Details
Attachments
(3 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020301
BuildID: 0.9.8 from source built on redhat 7.1
I created a page with a link on it that resized the frame in which it was
displayed ("mainframe") to allow another frame that is usually hidden with
height =0 ("hideframe"), to be seen. on executing the command to resize the
frame, mozilla reloads the files specified in the frameset file. after this
happens, referring to objects in "mainframe" from code in "hideframe" doesn't work.
Reproducible: Always
Steps to Reproduce:
1. create frameset containing files "mainframe" and "hideframe", mainframe
should contain a button or link that when clicked will run code like
""parent.document.body.rows = "50%,*";""
2.in hideframe create a button or link that will change the caption or text
in/on a control in "mainframe" and then resize the frame back to 0% height: ""<a
href='javascript: parent.mainframe.document.forms.meadd.recipe.value="test
text"; parent.document.body.rows="100%,*" ' >link text</a>"".
3. after one (or sometimes two) uses, i start getting "###!!! ASSERTION: cannot
get parentTop: 'parentTop', file nsGlobalWindow.cpp, line 3114
###!!! Break: at file nsGlobalWindow.cpp, line 3114"
and if I continue to try to use these pages I start getting "JavaScript error:
line 0: parent.mainframe.document has no properties"
4. this will not fail every single time but will fail at least 90% of the time
on my computer.
Actual Results: objects in one frame cannot refer to objects in another frame
if the site chooses to resize any of its frames.
I'd like to help with this fix and further development of mozilla. I am an
experienced developer with at least resonable exposure to linux development and
tools. I'd like to become involved in the mozilla project. I request that the
reciever of this message forward to me any known resolutions to this problem as
well as any information that may help me to assist the mozilla project.!
thanks
Fred
not jseng.
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
| Assignee | ||
Comment 2•24 years ago
|
||
A testcase would help to start with. Please attach the two frames to this bug
(click on create attachment) and then create a frameset document that referes to
the two frames you attached to this bug.
As for the problem, from what it sounds like I'm guessing that the fix for bug
52334 would get us a lot closer to fixing this since that takes care of
reloading iframes, and making us not reload frames when they're resized or
otherwise changed would be trivial once the fix for that bug lands, or maybe
I'll even include the fix for the frame case in the fix for that bug.
Comment 3•24 years ago
|
||
Fred, can you please create a simple test case for this?
It would be very helpful ...
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
Comment 7•24 years ago
|
||
Confirmed on that testcase in a CVS build from 2002-04-27.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•24 years ago
|
||
Fixed by checkin for bug 48422
Comment 11•24 years ago
|
||
fixed, even
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•